This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug symtab/15691] New: gdb crash from "Stay in DWO optimization"


http://sourceware.org/bugzilla/show_bug.cgi?id=15691

            Bug ID: 15691
           Summary: gdb crash from "Stay in DWO optimization"
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

When debugging a program with a mix of fission and non-fission object files,
gdb can crash here:

../../gdb-7.6.x/gdb/dwarf2read.c:4482: internal-error:
fill_in_sig_entry_from_dwo_entry: Assertion `sig_entry->per_cu.v.quick->symtab
== NULL' failed.

This happens when a TU from a non-DWO file is read first, and then gdb reads
debug info from a DWO file.  gdb thinks the debug info hasn't been read yet
when in fact it has.

[patch,testcase to follow]

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]