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: Improve separate debug file support for elfutils
Date: Sat, 14 Oct 2006 23:45:00 -0000	[thread overview]
Message-ID: <20061014234541.GA14820@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20061006202550.GA16735@nevyn.them.org>

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.


Thanks for info,
Jan


On Fri, 06 Oct 2006 22:25:50 +0200, Daniel Jacobowitz wrote:
> It turns out that elfutils's eu-strip differs from objcopy --only-keep-debug
> in one important respect: elfutils tends to leave .symtab in the original
> file and put a NOBITS copy in the separate debug file, but objcopy moves the
> whole symtab.  This difference shows up a problem in GDB.
> 
> We search for the section containing the PC in a bunch of places, mostly for
> overlay support (does this even still work?  no idea).  When we look up the
> section for the PC, we might find either the copy in the separate debug file
> or the original; they cover the same PC ranges.  So we need to allow the
> two sections to be treated as equal.  That's what this patch implements.
> I'm not sure how well it would work with overlays - but I don't see a way,
> even in theory, to do better.
> 
> The change to "info sym" is a cosmetic improvement, which I made while
> trying to find a way to test this portably.  The original test was on ARM
> with Thumb; we would try to look up the minsym to figure out whether to
> set a 2-byte or 4-byte breakpoint, and by failing to find the minsym,
> we set the wrong type.
> 
> I plan to commit this, probably next week, unless someone happens to have
> an idea for another solution.  Tested x86_64-pc-linux-gnu.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery
> 
> 2006-10-06  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* Makefile.in (symtab.o): Update.
> 	* symtab.h (matching_bfd_section): New prototype.
> 	* symtab.c (matching_bfd_section): New.
> 	(find_pc_sect_psymbol, find_pc_sect_symtab): Use it.
> 	* minsyms.c (lookup_minimal_symbol_by_pc_section): Likewise.
> 	* printcmd.c (sym_info): Ignore separate debug objfiles.
> 
> 2006-10-06  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* gdb.base/sepdebug.exp: Remove debug format test.
> 	* lib/gdb.exp (gdb_gnu_strip_debug): Perform debug format test.
> 	Handle no-symtab.
> 	* gdb.base/sepsymtab.c, gdb.base/sepsymtab.exp: New.
> 
[snip]


  reply	other threads:[~2006-10-14 23:45 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 [this message]
2006-10-15  1:29   ` Daniel Jacobowitz
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=20061014234541.GA14820@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