From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com,
ccoutant@google.com, saugustine@google.com
Subject: Crash regression for gdb.dwarf2/dw2-inheritance.exp [Re: [RFA 3/3] Initial Fission support, the actual Fission stuff]
Date: Sun, 29 Apr 2012 09:05:00 -0000 [thread overview]
Message-ID: <20120429085754.GA9548@host2.jankratochvil.net> (raw)
In-Reply-To: <20120418185738.277DB2461AF@ruffy.mtv.corp.google.com>
On Wed, 18 Apr 2012 20:57:38 +0200, Doug Evans wrote:
> 2012-04-18 Doug Evans <dje@google.com>
>
> Initial support for Fission. http://gcc.gnu.org/wiki/DebugFission
Running gdb/testsuite/gdb.dwarf2/dw2-inheritance.exp ...
-PASS: gdb.dwarf2/dw2-inheritance.exp: ptype inherited
+ERROR: couldn't load /unsafegdb/testsuite.unix.-m32/gdb.dwarf2/dw2-inheritance.x into /unsafegdb/testsuite.unix.-m32/../../gdb/gdb (end of file).
+ERROR: Couldn't send ptype inherited to GDB.
+UNRESOLVED: gdb.dwarf2/dw2-inheritance.exp: ptype inherited
Program terminated with signal 11, Segmentation fault.
#0 0x000000000063037c in dwarf_decode_line_header (offset=0, cu=0x2c4b410) at dwarf2read.c:12320
12320 abfd = section->asection->owner;
(gdb) p section->asection
$2 = (asection *) 0x0
(gdb) bt
#0 0x000000000063037c in dwarf_decode_line_header (offset=0, cu=0x2c4b410) at dwarf2read.c:12320
#1 0x000000000061c354 in dwarf2_build_include_psymtabs (cu=0x2c4b410, die=0x2c4b5d0, pst=0x2c2d810) at dwarf2read.c:3324
#2 0x000000000061e46b in process_psymtab_comp_unit_reader (reader=0x7fff3fa1ac90, info_ptr=0x2c2d777 "\003base", comp_unit_die=0x2c4b5d0, has_children=1,
data=0x0) at dwarf2read.c:4159
#3 0x000000000061dc53 in init_and_read_dies_worker (this_cu=0x2c2d7a0, use_existing_cu=0, keep=0, die_reader_func=
0x61e036 <process_psymtab_comp_unit_reader>, data=0x0) at dwarf2read.c:3895
#4 0x000000000061dd12 in init_cu_and_read_dies (this_cu=0x2c2d7a0, use_existing_cu=0, keep=0, die_reader_func=0x61e036 <process_psymtab_comp_unit_reader>,
data=0x0) at dwarf2read.c:3936
#5 0x000000000061e4f9 in process_psymtab_comp_unit (this_cu=0x2c2d7a0) at dwarf2read.c:4178
#6 0x000000000061e726 in dwarf2_build_psymtabs_hard (objfile=0x2c386d0) at dwarf2read.c:4269
#7 0x000000000061bca2 in dwarf2_build_psymtabs (objfile=0x2c386d0) at dwarf2read.c:3133
#8 0x0000000000508db2 in read_psyms (objfile=0x2c386d0) at elfread.c:1449
#9 0x000000000058f9be in require_partial_symbols (objfile=0x2c386d0, verbose=0) at psymtab.c:92
It happens on RHEL-6 i386/x86_68/x86_64-m32. Feel free to request more info.
Regards,
Jan
next prev parent reply other threads:[~2012-04-29 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 19:12 [RFA 3/3] Initial Fission support, the actual Fission stuff Doug Evans
2012-04-19 5:07 ` Doug Evans
2012-04-27 18:29 ` Tom Tromey
2012-04-19 10:25 ` Yao Qi
2012-04-19 15:28 ` Doug Evans
2012-04-27 18:38 ` Tom Tromey
2012-04-27 18:20 ` Tom Tromey
2012-04-28 23:59 ` Doug Evans
2012-04-29 9:05 ` Jan Kratochvil [this message]
2012-04-30 0:06 ` Crash regression for gdb.dwarf2/dw2-inheritance.exp [Re: [RFA 3/3] Initial Fission support, the actual Fission stuff] Doug Evans
2012-04-30 2:07 ` Jan Kratochvil
2012-04-30 14:30 ` Doug Evans
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=20120429085754.GA9548@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.com \
--cc=tromey@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