From: Alan Modra <amodra@bigpond.net.au>
To: Vivek Goyal <vgoyal@in.ibm.com>,
gdb@sourceware.org, Dave Anderson <anderson@redhat.com>,
binutils@sourceware.org
Subject: Re: "gdb vmlinux" gives wrong symbol addresses
Date: Mon, 21 Aug 2006 01:38:00 -0000 [thread overview]
Message-ID: <20060821013829.GA20576@bubble.grove.modra.org> (raw)
In-Reply-To: <20060818184837.GA1980@nevyn.them.org>
On Fri, Aug 18, 2006 at 02:48:37PM -0400, Daniel Jacobowitz wrote:
> The debug section has been fully resolved, but relocations are also
> applied to it, moving all addresses up even further. I don't have
> any good idea on how to detect this case. We originally handled
> relocations for shared libraries with unrelocated debug sections;
> but this is a fully relocated section which still has relocation
> information.
>
> Did we change all binutils targets to resolve relocations in debug
> sections? I don't really remember. If so, maybe we should drop
> support for shared libraries with this problem, and only apply
> relocations to debug info for ET_REL objects.
I think that for ET_EXEC and ET_DYN gdb should ignore relocs that use
the normal symbol table. Sane ELF targets will have dynamic reloc
section(s) with sh_link pointing at a symtab section with sh_type of
SHT_DYNSYM. --emit-relocs creates reloc sections with sh_link pointing
at a symtab section with sh_type of SHT_SYMTAB.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2006-08-21 1:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 18:38 Vivek Goyal
2006-08-18 18:48 ` Daniel Jacobowitz
2006-08-18 19:15 ` Vivek Goyal
2006-08-21 1:38 ` Alan Modra [this message]
2006-08-21 1:54 ` Daniel Jacobowitz
2006-08-21 3:24 ` Alan Modra
2006-08-23 17:33 ` Jan Kratochvil
2006-08-23 18:31 ` Mark Kettenis
2006-08-23 18:36 ` Daniel Jacobowitz
2006-08-21 15:15 ` Vivek Goyal
2006-08-21 15:25 ` Daniel Jacobowitz
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=20060821013829.GA20576@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=anderson@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=vgoyal@in.ibm.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