From: Michael Eager <eager@eagercon.com>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: Incorrect breakpoint address w no stabs
Date: Tue, 03 Oct 2006 04:41:00 -0000 [thread overview]
Message-ID: <4521E9E1.6060706@eagercon.com> (raw)
In-Reply-To: <1159845003.9761.35.camel@localhost.localdomain>
Michael Snyder wrote:
> On Mon, 2006-10-02 at 19:38 -0700, Michael Eager wrote:
>> Quick follow-up.
>>
>> This problem doesn't happen if all object files use
>> DWARF or no debugging. If the executable has mixed
>> stabs/DWARF, then the problem shows up.
>
> What about if all object files use stabs?
There's almost always assembly files (without stabs) which
are linked after the rest of the code. Breakpoints at
symbols in those files will be incorrect.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2006-10-03 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 17:47 Michael Eager
2006-10-01 18:16 ` Daniel Jacobowitz
2006-10-01 20:50 ` Michael Eager
2006-10-01 23:23 ` Daniel Jacobowitz
2006-10-03 2:38 ` Michael Eager
2006-10-03 3:10 ` Michael Snyder
2006-10-03 4:41 ` Michael Eager [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=4521E9E1.6060706@eagercon.com \
--to=eager@eagercon.com \
--cc=Michael.Snyder@palmsource.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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