From: Harald Koenig <H.Koenig@science-computing.de>
To: Harald Koenig <H.Koenig@science-computing.de>
Cc: Pedro Alves <pedro@codesourcery.com>,
bug-gdb@gnu.org, gdb-patches@sourceware.org,
Harald Koenig <koenig@science-computing.de>
Subject: Re: some compile errors fo gdb-7.0.1
Date: Tue, 23 Feb 2010 17:14:00 -0000 [thread overview]
Message-ID: <20100223171348.GA31492@atuin.science-computing.de> (raw)
In-Reply-To: <20100223163505.GA21619@atuin.science-computing.de>
Hi,
here is a problem report for break points on AIX 5.1 and 5.3.
first AIX 5.3:
if a program first runs in gdb without any break points and finished,
then it's not possible to set break a break point for the next run
(this is the same on AIX 5.1 too):
# gdb a.out
GNU gdb (GDB) 7.1.50.20100222-cvs
Reading symbols from a.out...done.
(gdb) r
Starting program: a.out
hello
Program exited normally.
(gdb) b main
==> Cannot access memory at address 0xf00d7530
(gdb) q
with bogus address "0xf00d7530"
if there is a(ny) break point set for the 1st run things seem to work fine:
# gdb a.out
GNU gdb (GDB) 7.1.50.20100222-cvs
Reading symbols from a.out...done.
(gdb) b main
Breakpoint 1 at 0x100003c8: file hello.c, line 23.
(gdb) r
Starting program: a.out
Breakpoint 1, main (argc=1, argv=0x2ff22578, env=0x2ff22580) at hello.c:23
23 main(int argc...
(gdb) c
Continuing.
hello
Program exited normally.
(gdb) r
Starting program: a.out
Breakpoint 1, main (argc...=1, argv=0x2ff22578, env=0x2ff22580) at hello.c:23
23 main(int argc, ...
(gdb) c
Continuing.
hello
Program exited normally.
(gdb) b main
Note: breakpoint 1 also set at pc 0x100003c8.
Breakpoint 2 at 0x100003c8: file hello.c, line 23.
(gdb) r
Starting program: a.out
Breakpoint 1, main (argc=1, argv=0x2ff22578, env=0x2ff22580) at hello.c:23
23 main(int argc, ...
(gdb) c
Continuing.
hello
Program exited normally.
(gdb)
===============================================================================
on AIX 5.1 though setting a break point before the first run
only seems to work, but that break point is not functional for the 1st run:
Reading symbols from a.out...done.
(gdb) b main
Breakpoint 1 at 0x100003c8: file hello.c, line 23.
(gdb) i b
Num Type Disp Enb Address What
1 breakpoint keep y 0x100003c8 in main at hello.c:23
(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) i b
Num Type Disp Enb Address What
1 breakpoint keep y 0x100003c8 in main at hello.c:23
and that break point doesn't function either in a 2nd run:
(gdb) r
Starting program: a.out
hello
Program exited normally.
but if I add another bp to main (or another function) gdb starts to work "better";)
(gdb) i b
Num Type Disp Enb Address What
1 breakpoint keep n 0x100003c8 in main at hello.c:23
(gdb) b main
Note: breakpoint 1 (disabled) also set at pc 0x100003c8.
Breakpoint 2 at 0x100003c8: file hello.c, line 23.
(gdb) r
Starting program: a.out
Breakpoint 2, main (argc=1, argv=0x2ff2248c, env=0x2ff22494) at hello.c:23
23 main(int argc,...
(gdb) i b
Num Type Disp Enb Address What
1 breakpoint keep n 0x100003c8 in main at hello.c:23
2 breakpoint keep y 0x100003c8 in main at hello.c:23
breakpoint already hit 1 time
(gdb) c
Continuing.
hello
Program exited normally.
(gdb) r
Starting program: a.out
Breakpoint 2, main (argc=1, argv=0x2ff2248c, env=0x2ff22494) at hello.c:23
23 main(int argc,...
(gdb) c
Continuing.
hello
Program exited normally.
(gdb)
any thoughts about that breakpoint weirdnes son AIX ?!?
right now I'm trying to build gdb on AIX 6.1 which right now fails here
"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.
where the source reads like this -- hmmmmm....
/* getthrds(3) isn't prototyped in any AIX 4.3.3 #include file. */
extern int getthrds (pid_t, struct thrdsinfo64 *,
int, pthdb_tid_t *, int);
but now I have to leave for today -- stay tuned ;-))
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-23 17:14 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 ` 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 [this message]
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
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=20100223171348.GA31492@atuin.science-computing.de \
--to=h.koenig@science-computing.de \
--cc=bug-gdb@gnu.org \
--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