From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-12323-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 6567 invoked by alias); 20 Sep 2012 20:49:22 -0000
Received: (qmail 6528 invoked by uid 48); 20 Sep 2012 20:49:21 -0000
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/14601] New: segv when reading
 DW_TAG_imported_declaration,module
Date: Thu, 20 Sep 2012 20:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: symtab
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-14601-4717@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2012-q3/txt/msg00374.txt.bz2


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.