From: Harald Koenig <H.Koenig@science-computing.de>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Harald Koenig <H.Koenig@science-computing.de>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org,
Harald Koenig <koenig@science-computing.de>
Subject: Re: Build errors on AIX
Date: Wed, 24 Feb 2010 14:09:00 -0000 [thread overview]
Message-ID: <20100224140849.GA14754@atuin.science-computing.de> (raw)
In-Reply-To: <201002241335.07011.pedro@codesourcery.com>
On Feb 24, Pedro Alves wrote:
> > > "gdb-CVS-20100222/gdb/aix-thread.c", line 352.46: 1506-280 (W) Function argument assignment between types "int*" and "unsigned int*" is not allowed.
> ^^^^^^
>
> How does one read that? line 352, column 46? On my sources,
oops, cut'n'paste error from the log file -- sorry!
yes. that's a (W)arning in line 352, don't care;)
the real error msg was this one -- fix is in my last mail:
"gdb-CVS-20100222/gdb/aix-thread.c", line 651.14: 1506-343 (S) Redeclaration of getthrds differs from previous declaration on line 904 of "/usr/include/procinfo.h".
> I can't really guess exactly what's going on here. AIX/RS6000
> is probably the port that most needs love of all the supported
> ports. E.g, I wouldn't be surprised if recent changes like PIE
> or multi-program support and the revamping around these broke
> this port, for it does things in non-standard ways. These
> commands may offer some clues:
>
> "(gdb) maint info breakpoints"
> "(gdb) set debug infrun 1"
> "(gdb) set target infrun 1"
(gdb) set target infrun 1
Ambiguous set command "target infrun 1": target-async, target-charset, target-wide-charset.
so:
(gdb) set debug infrun 1
(gdb) r
Starting program: a.out
infrun: proceed (addr=0xffffffff, signal=0, step=0)
infrun: resume (step=0, signal=0), trap_expected=0
hello
infrun: wait_for_inferior (treat_exec_as_sigtrap=0)
infrun: target_wait (-1, status) =
infrun: 356558 [process 356558],
infrun: status->kind = exited, status = 9
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_EXITED
Program exited with code 011.
infrun: stop_stepping
(gdb) maint info breakpoints
Num Type Disp Enb Address What
-1 thread events keep y 0xd04b37e8 <__pthread_init> inf 1
(gdb) b main
Cannot access memory at address 0xf0322508
(gdb) maint info breakpoints
Num Type Disp Enb Address What
-1 thread events keep y 0xd04b37e8 <__pthread_init> inf 1
(gdb) b main
Cannot access memory at address 0xf0322508
(gdb)
and for AIX 5.1:
gdb a.out
GNU gdb (GDB) 7.1.50.20100222-cvs
Reading symbols from a.out...(no debugging symbols found)...done.
(gdb) b main
Breakpoint 1 at 0x1000039c
(gdb) maint info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep y 0x1000039c <main+32> inf 1
(gdb) r
Starting program: a.out
Error in re-setting breakpoint 1: Cannot access memory at address 0x0
Error in re-setting breakpoint 1: Cannot access memory at address 0x0
hello
Program exited normally.
(gdb) r
Starting program: a.out
hello
Program exited normally.
(gdb) maint info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep n 0x1000039c <main+32> inf 1
-1 thread events keep y 0xd0347e44 <__pthread_init> inf 1
(gdb) r
Starting program: a.out
hello
Program exited normally.
(gdb) b main
Note: breakpoint 1 (disabled) also set at pc 0x1000039c.
Breakpoint 2 at 0x1000039c
(gdb) maint info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep n 0x1000039c <main+32> inf 1
-1 thread events keep y 0xd0347e44 <__pthread_init> inf 1
2 breakpoint keep y 0x1000039c <main+32> inf 1
(gdb) r
Starting program: a.out
Breakpoint 2, 0x1000039c in main ()
(gdb)
ah, I just notice that bp #1 got disabled (likely because of that "Error in re-setting breakpoint 1: Cannot access memory at address 0x0").
instead of a 2nd "b main" it also works to enable #1 with "en b 1" ...
> If you have an older gdb that works, I think we get to
> debug the new gdb to try to track this down.
yes, our gdb-6.8 binary works just fine for me on AIX 5.1++ ...
Harald Koenig
--
"I hope to die ___ _____
before I *have* to use Microsoft Word.", 0--,| /OOOOOOO\
Donald E. Knuth, 02-Oct-2001 in Tuebingen. <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig \/\/\/\/\/\/\/\/\/
science+computing ag // / \\ \
koenig@science-computing.de ^^^^^ ^^^^^
--
Vorstand/Board of Management:
Dr. Bernd Finkbeiner, Dr. Roland Niemeier,
Dr. Arno Steitz, Dr. Ingrid Zech
Vorsitzender des Aufsichtsrats/
Chairman of the Supervisory Board:
Michel Lepert
Sitz/Registered Office: Tuebingen
Registergericht/Registration Court: Stuttgart
Registernummer/Commercial Register No.: HRB 382196
next prev parent reply other threads:[~2010-02-24 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100215141621.GA9469@atuin.science-computing.de>
2010-02-18 19:23 ` some compile errors fo gdb-7.0.1 Pedro Alves
2010-02-23 15:22 ` Harald Koenig
2010-02-23 17:08 ` Pedro Alves
2010-02-23 16:35 ` Harald Koenig
2010-02-23 17:14 ` Harald Koenig
2010-02-24 12:51 ` Harald Koenig
2010-02-24 13:35 ` Build errors on AIX Pedro Alves
2010-02-24 14:09 ` Harald Koenig [this message]
2010-03-01 6:47 ` Joel Brobecker
2010-03-01 6:51 ` some compile errors fo gdb-7.0.1 Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100224140849.GA14754@atuin.science-computing.de \
--to=h.koenig@science-computing.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=koenig@science-computing.de \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox