From: Daniel Jacobowitz <drow@false.org>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: gdb@sourceware.org, Dave Anderson <anderson@redhat.com>,
binutils@sourceware.org
Subject: Re: "gdb vmlinux" gives wrong symbol addresses
Date: Mon, 21 Aug 2006 15:25:00 -0000 [thread overview]
Message-ID: <20060821152542.GA21118@nevyn.them.org> (raw)
In-Reply-To: <20060821151439.GF9549@in.ibm.com>
On Mon, Aug 21, 2006 at 11:14:39AM -0400, Vivek Goyal wrote:
> On Sun, Aug 20, 2006 at 09:54:30PM -0400, Daniel Jacobowitz wrote:
> > On Mon, Aug 21, 2006 at 11:08:29AM +0930, Alan Modra wrote:
> > > 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.
> >
> > This amounts to always ignoring relocations; GDB only uses relocations
> > for debug sections, which will never point at SHT_DYNSYM (I don't
> > think?).
> >
>
> This brings me to a stupid question. Why do I have to apply relocations
> for file type ET_EXEC. By definition, doesn't it mean that all the
> relocations have already been processed?
For ET_EXEC, you don't especially. However, for some ET_DYN you do and
some ET_DYN you don't. If we're going to change the behavior... let's
get it right.
I just need to figure out how to do the check Alan suggested without
breaking non-ELF GDB. Shouldn't be too hard.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-08-21 15:25 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
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 [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=20060821152542.GA21118@nevyn.them.org \
--to=drow@false.org \
--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