This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [review] Fix backtrace of prelinked libc with separate debuginfo


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]