From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Improve separate debug file support for elfutils
Date: Tue, 17 Oct 2006 20:32:00 -0000 [thread overview]
Message-ID: <20061017203214.GA11728@nevyn.them.org> (raw)
In-Reply-To: <20061006202550.GA16735@nevyn.them.org>
On Fri, Oct 06, 2006 at 04:25:50PM -0400, Daniel Jacobowitz wrote:
> It turns out that elfutils's eu-strip differs from objcopy --only-keep-debug
> in one important respect: elfutils tends to leave .symtab in the original
> file and put a NOBITS copy in the separate debug file, but objcopy moves the
> whole symtab. This difference shows up a problem in GDB.
>
> We search for the section containing the PC in a bunch of places, mostly for
> overlay support (does this even still work? no idea). When we look up the
> section for the PC, we might find either the copy in the separate debug file
> or the original; they cover the same PC ranges. So we need to allow the
> two sections to be treated as equal. That's what this patch implements.
> I'm not sure how well it would work with overlays - but I don't see a way,
> even in theory, to do better.
>
> The change to "info sym" is a cosmetic improvement, which I made while
> trying to find a way to test this portably. The original test was on ARM
> with Thumb; we would try to look up the minsym to figure out whether to
> set a 2-byte or 4-byte breakpoint, and by failing to find the minsym,
> we set the wrong type.
I've checked this in; it's separate from the issue Jan reported for
relocatable files.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-17 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 20:26 Daniel Jacobowitz
2006-10-14 23:45 ` Jan Kratochvil
2006-10-15 1:29 ` Daniel Jacobowitz
2006-10-17 20:32 ` Daniel Jacobowitz [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=20061017203214.GA11728@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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