public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-14601-4717@http.sourceware.org/bugzilla/> (raw)


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.


             reply	other threads:[~2012-09-20 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 20:49 dje at google dot com [this message]
2012-09-20 20:52 ` [Bug symtab/14601] " dje at google dot com
2012-10-03 17:05 ` cvs-commit at gcc dot gnu.org
2012-10-03 17:07 ` dje at google dot com

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=bug-14601-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).