From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, jakub@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: Improve separate debug file support for elfutils
Date: Sun, 15 Oct 2006 01:29:00 -0000 [thread overview]
Message-ID: <20061015012949.GA28974@nevyn.them.org> (raw)
In-Reply-To: <20061014234541.GA14820@host0.dyn.jankratochvil.net>
On Sun, Oct 15, 2006 at 01:45:41AM +0200, Jan Kratochvil wrote:
> Hi Daniel,
>
> thanks for this patch. Unfortunately using CVS + this patch the problem is
> still present:
> Reading symbols from /lib/modules/2.6.18-1.2747.fc6/kernel/fs/ext3/ext3.ko...Reading symbols from /usr/lib/debug/lib/modules/2.6.18-1.2747.fc6/kernel/fs/ext3/ext3.ko.debug...DW_FORM_strp pointing outside of .debug_str section [in module /usr/lib/debug/lib/modules/2.6.18-1.2747.fc6/kernel/fs/ext3/ext3.ko.debug]
>
> These two testfiles stored at:
> http://www.jankratochvil.net/priv/ext3-debug.tar.gz
>
> According to the error I believe the patch also needs to cover libbfd.
> Is it valid it still needs to be patched for this case?
>
> Jakub Jelinek was confirming before that elfutils produce in some way valid
> ELFs - with the missing strtab/symtab. I did not check the binaries myself.
I didn't even know it was possible to put a .gnu_debuglink in a
relocatable file! So this is a different problem than the one I was
working on, I suppose.
I presume from the error message that
bfd_simple_get_relocated_section_contents hasn't relocated the file's
debug info. You'll see that it takes a symbol_table. You could
probably arrange to supply one from the alternate file. I'm worried
that the section offsets would not match up, though, because section
numbering changes.
Simply put, I do not understand how Jakub can describe this file as
valid. The ext3.ko.debug has relocation sections with an sh_link
pointing to the NOBITS symtab. And that symtab isn't in that file, and
at least one section has a different section index between the two
files, so I don't see how you can trust that a symtab from another file
is useful in this one.
You get lucky, in that only .module_sig moved and there's only one
symbol in it (symbol #321), and there's no relocations against the
debug sections.
Jakub, how do you expect this weird file to be interpreted (and why are
you producing things that BFD can't handle, anyway?)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-15 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 20:26 Daniel Jacobowitz
2006-10-14 23:45 ` Jan Kratochvil
2006-10-15 1:29 ` Daniel Jacobowitz [this message]
2006-10-17 20:32 ` 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=20061015012949.GA28974@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
--cc=jan.kratochvil@redhat.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