From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: debug problem with prelinked libraries
Date: Fri, 07 May 2010 13:23:00 -0000 [thread overview]
Message-ID: <20100507132310.GA6374@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4BE187D8.4050804@codesourcery.com>
On Wed, 05 May 2010 16:59:36 +0200, Andrew Stubbs wrote:
> > prelink includes code to manipulate the contents of the debug info.
[...]
> Maybe prelink has failed to relocate the debug info in this case?
The attached patch should fix it.
Although SHT_MIPS_DWARF value should be recognized only for e_machine as
EM_MIPS or EM_MIPS_RS3_LE or EM_MIPS_X? Or are there some other rules?
Regards,
Jan
--- prelink/src/dso.c-orig 2010-04-13 16:41:15.000000000 +0200
+++ prelink/src/dso.c 2010-05-07 15:16:25.000000000 +0200
@@ -1381,6 +1381,7 @@ adjust_dso (DSO *dso, GElf_Addr start, G
switch (dso->shdr[i].sh_type)
{
case SHT_PROGBITS:
+ case SHT_MIPS_DWARF:
name = strptr (dso, dso->ehdr.e_shstrndx, dso->shdr[i].sh_name);
if (strcmp (name, ".stab") == 0
&& adjust_stabs (dso, i, start, adjust))
next prev parent reply other threads:[~2010-05-07 13:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 12:48 Andrew Stubbs
2010-05-05 14:35 ` Daniel Jacobowitz
2010-05-05 14:59 ` Andrew Stubbs
2010-05-07 13:23 ` Jan Kratochvil [this message]
2010-05-07 13:26 ` Andrew Stubbs
2010-07-01 15:43 ` Thomas Schwinge
2010-07-06 9:59 ` MIPS: 64-bit DWARF (was: debug problem with prelinked libraries) Thomas Schwinge
2010-07-14 8:50 ` MIPS: 64-bit DWARF Thomas Schwinge
2010-07-14 16:56 ` David Daney
2010-07-14 18:44 ` Maciej W. Rozycki
2010-07-15 15:48 ` Tom Tromey
2010-07-16 14:44 ` Maciej W. Rozycki
2010-07-21 22:54 ` Joseph S. Myers
2010-07-22 5:28 ` Tom Tromey
2010-07-16 11:22 ` Thomas Schwinge
2010-07-19 20:00 ` Richard Sandiford
2010-07-22 7:41 ` Thomas Schwinge
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=20100507132310.GA6374@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=ams@codesourcery.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