From: Daniel Jacobowitz <drow@false.org>
To: Ananth Sowda <asowda@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: DSO with relocations and GDB.
Date: Mon, 21 Apr 2008 23:34:00 -0000 [thread overview]
Message-ID: <20080421183241.GA19774@caradoc.them.org> (raw)
In-Reply-To: <c92b40c80804211126h1fc8a79fk90f1aa5fc1bfb4a0@mail.gmail.com>
On Mon, Apr 21, 2008 at 11:26:03AM -0700, Ananth Sowda wrote:
> On 4/18/08, Daniel Jacobowitz <drow@false.org> wrote:
> > On Fri, Apr 18, 2008 at 03:50:00PM -0700, Ananth Sowda wrote:
> > > The powerpc eabi DSO (dynamic shared object) I'm debugging using GDB
> > > 6.6 has .debug_info and other debug tables which have unresolved
> > > relocations. The .rela_debug_info is available in the DSO and it has
> > > sh_link set to .symtab, sh_info to .debug_info. However, the bfd code
> > > in GDB 6.6 does not seem to associate the .debug_info with
> > > corresponding .rela_debug.info section. When GDB attempts to relocate
> > > these debug tables, bfd does not recognize that the section has
> > > relocations.
> >
> > What does objdump -h say about this file? IOW, what do you mean by
> > "does not seem to associate"?
>
> BFD internal section data structure for .debug_info section is not
> marked with SEC_RELOC in flags and number of relocation records for
> the section is 0. objdump -h output shows that sh_link(points to
> .symtab) and sh_link(points to .debug_info) are set correctly for the
> .rela_debug.info section.
That's the real problem; you may want to ask the binutils list
or debug how with sh_link/sh_info set there is still no SEC_RELOC
flag.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-21 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 2:39 Ananth Sowda
2008-04-20 9:09 ` Daniel Jacobowitz
2008-04-21 23:26 ` Ananth Sowda
2008-04-21 23:34 ` Daniel Jacobowitz [this message]
2008-04-22 20:09 ` Ananth Sowda
2008-04-23 7:28 ` 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=20080421183241.GA19774@caradoc.them.org \
--to=drow@false.org \
--cc=asowda@gmail.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