From: Jan Kratochvil <lace@jankratochvil.net>
To: gdb-patches@sources.redhat.com
Subject: [patch] Fix gdb crash on some missing ELF debug info
Date: Fri, 23 Jun 2006 10:37:00 -0000 [thread overview]
Message-ID: <20060623103735.GA28356@host0.dyn.jankratochvil.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hi,
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196439
On Fedora Core 5:
gdb /usr/lib/valgrind/x86-linux/memcheck
break _start_in_C
run
segfaults as the file's debug info references location list while no
".debug_loc" section exists there.
eu-readelf -w /usr/lib/valgrind/x86-linux/memcheck
DWARF section '.debug_info' at offset 0x14759c:
...
[ 176d4] subprogram
...
name "_start_in_C"
...
frame_base location list [ 116d7]
Trivia complaint on the file coherency, no frame_info debugging available for
such functions.
Regards,
Jan Kratochvil
[-- Attachment #2: gdb-cvs20060623-debug_loc.patch --]
[-- Type: text/plain, Size: 1195 bytes --]
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196439
Fedora Core 5:
gdb /usr/lib/valgrind/x86-linux/memcheck
break _start_in_C
run
segfault
eu-readelf -w /usr/lib/valgrind/x86-linux/memcheck
DWARF section '.debug_info' at offset 0x14759c:
...
[ 176d4] subprogram
...
name "_start_in_C"
...
frame_base location list [ 116d7]
corrupted as no location lists (.debug_loc) exist there at all.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.199
diff -u -p -r1.199 dwarf2read.c
--- dwarf2read.c 14 Jun 2006 15:06:35 -0000 1.199
+++ dwarf2read.c 23 Jun 2006 10:28:44 -0000
@@ -9324,7 +9324,9 @@ static void
dwarf2_symbol_mark_computed (struct attribute *attr, struct symbol *sym,
struct dwarf2_cu *cu)
{
- if (attr->form == DW_FORM_data4 || attr->form == DW_FORM_data8)
+ if ((attr->form == DW_FORM_data4 || attr->form == DW_FORM_data8)
+ /* DW_UNSND (attr) != 0 would produce non-zero bogus ->size & ->data */
+ && dwarf2_per_objfile->loc_size)
{
struct dwarf2_loclist_baton *baton;
next reply other threads:[~2006-06-23 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 10:37 Jan Kratochvil [this message]
2006-06-23 12:39 ` Daniel Jacobowitz
2006-06-23 13:08 ` Jan Kratochvil
2006-06-23 13:13 ` Daniel Jacobowitz
2006-07-12 21:15 ` Daniel Jacobowitz
2006-07-20 16:17 ` Joel Brobecker
2006-08-28 20:48 ` [patch] Testcase for missing ELF debug info [Re: [patch] Fix gdb crash on some missing ELF debug info] Jan Kratochvil
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=20060623103735.GA28356@host0.dyn.jankratochvil.net \
--to=lace@jankratochvil.net \
--cc=gdb-patches@sources.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