This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/14601] New: segv when readingDW_TAG_imported_declaration,module
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 20 Sep 2012 20:49:20 +0000
- Subject: [Bug symtab/14601] New: segv when readingDW_TAG_imported_declaration,module
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14601
Bug #: 14601
Summary: segv when reading DW_TAG_imported_declaration,module
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
AssignedTo: unassigned@sourceware.org
ReportedBy: dje@google.com
Classification: Unclassified
buildsym.c:using_directive is assumed to be NULL at the start of symbol
processing. Not all code paths ensure this. If a
DW_TAG_imported_declaration,module happens outside of finish_block_internal or
push_context, it won't get reset back to NULL, leaving a potentially dangling
value.
To see the crash you need to compile the testcase with -fdebug-types-section,
but there's nothing inherently dwarf4 or even dwarf-specific here.
bash$ gdb -nx testsuite/gdb.cp/using-crash
(gdb) b foo
(gdb) run
(gdb) kill
(gdb) file testsuite/gdb.cp/using-crash
Load new symbol table from "/foo/testsuite/gdb.cp/using-crash"? (y or n) y
Reading symbols from /foo/testsuite/gdb.cp/using-crash...done.
Segmentation fault
Patch to follow.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.