Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [review] Fix backtrace of prelinked libc with separate debuginfo
Date: Thu, 11 Jan 2007 22:17:00 -0000	[thread overview]
Message-ID: <20070111221725.GA12498@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20070109224323.GJ30631@nevyn.them.org>

On Tue, 09 Jan 2007 23:43:23 +0100, Daniel Jacobowitz wrote:
> On Sun, Oct 29, 2006 at 11:39:12PM +0100, Jan Kratochvil wrote:
> > It is (I believe) due to the fact the system libc gets prelinked to some
> > address but the separate debuginfo file is not updated for the prelinked
> > address.  `matching_bfd_sections' will fail to match afterwards.
> > 
> > Not sure if the testcase properly fails on all systems, it works for me with
> > the prelinking in effect.
> 
> Right.  It won't fail on Debian even with prelinking

I was trying to figure it out but there are too many combinations and without
the system available... While my patch was for matching_bfd_sections() (not
present in gdb-6.5 and therefore neither in debian-unstable) I imported
matching_bfd_sections() specifically to fix this bug before as it was easier
than without the matching_bfd_sections() patch.


> - I think this is
> because Debian uses binutils' objcopy program, which puts the stripped
> symbols in the debug file, but eu-strip leaves them only in the
> original file.  Which seems pretty strange but that's what it does.

The libbfd backward compatibility was recently restored by elfutils.
Currently a partial symtab copy is being made:

* Wed Oct 11 2006 Roland McGrath <roland@redhat.com> - 0.124-1
- eu-strip -f: copy symtab into debuginfo file when relocs use it

...
> I updated the test case to work with remote targets and then checked
> this in.

Thanks.


Regards,
Jan


  reply	other threads:[~2007-01-11 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 22:39 Jan Kratochvil
2007-01-09 22:43 ` Daniel Jacobowitz
2007-01-11 22:17   ` Jan Kratochvil [this message]
2007-01-12  1:22     ` 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=20070111221725.GA12498@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=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