From: Jesse Marlin <jesse.marlin@intec.us>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb 6.5 on AIX 5.3 not hitting breakpoints
Date: Wed, 15 Nov 2006 15:58:00 -0000 [thread overview]
Message-ID: <455B38A9.7060609@intec.us> (raw)
In-Reply-To: <20061115060918.GN3529@adacore.com>
I have never seen this behavior with gdb with any other unices, but this
is the first time we have run it on AIX.
I built the daily snapshot gdb 6.5.50.20061115. I tried with a simple
program and it worked:
--------------------------
(gdb) br main
Breakpoint 1 at 0x100003f4: file errno.c, line 11.
(gdb) run
Starting program: /home/cgi/errno_aix
Breakpoint 1, main (argc=1, argv=0x2ff20084) at errno.c:11
11 sscanf (argv[1], "%d", &err);
(gdb)
--------------------------
Then I tried with one of our more complicated programs and I see the
behavior with it ignoring the breakpoints:
--------------------------
(gdb) br main
Breakpoint 1 at 0x10000a90: file cgr_heartbeat_utl.c, line 223.
(gdb) run
Starting program: /u01/obj/dcs/misc/bin/cgr_heartbeat_utl
Breakpoint 1 at 0x100000a90: file cgr_heartbeat_utl.c, line 223.
HEARTBEAT>
--------------------------
I am wondering if it isn't some weird linker options that are screwing
it up or maybe we are missing some linker options. Any ideas?
Joel Brobecker wrote:
>>I have built gdb-6.5 on AIX 5.3 and have noticed that it is not hitting
>>breakpoints. Is this a known problem and if so is there any workaround?
>
>
> As far as I can tell, appart from an unexpected warnings about the OS
> ABI which I will try to investigate when I have some time, the HEAD
> debugger from CVS seems to be working fine:
>
> (gdb) b break_me
> Breakpoint 1 at 0x100003e4: file foo.c, line 6.
> (gdb) run
> Starting program: /home/brobecke/test/ex/foo
>
> Breakpoint 1, break_me () at foo.c:6
> 6 printf ("Hello world\n");
>
> I suggest trying the debugger from CVS, and if that doesn't work,
> then maybe trying to post more information about what compiler you
> used (I assumed GCC), which version, and provide a complete example
> that demonstrates the problem (sources and compilation switches that
> you used to build the example).
>
--
Jesse L. Marlin Phone: +1 404-705-2912
Senior Software Developer
Intec Billing, Inc
Web: http://www.intecbilling.com/
Email: jesse.marlin@intecbilling.com
Suite 200, 301 Perimeter Center, Atlanta, GA 30346 USA
This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful.
Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
prev parent reply other threads:[~2006-11-15 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 19:19 Jesse Marlin
2006-11-15 5:00 ` Joel Brobecker
2006-11-15 6:09 ` Joel Brobecker
2006-11-15 15:58 ` Jesse Marlin [this message]
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=455B38A9.7060609@intec.us \
--to=jesse.marlin@intec.us \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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