RE: Crash triggered by DWARF debug info: Any ideas ?

[Kai Schuetz <Kai dot Schuetz at synopsys dot com>]

Hi Tom,

> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com]
> Sent: Tuesday, February 12, 2013 20:25
> To: Kai Schuetz
> Cc: gdb@sourceware.org
> Subject: Re: Crash triggered by DWARF debug info: Any ideas ?
> 
> >>>>> "Kai" == Kai Schuetz <Kai.Schuetz@synopsys.com> writes:
> 
> Kai> I'm looking into some crash in gdb 7.5.1 in the DWARF reader.
> Kai> The DWARF (v3) debug info in the case is pretty basic (it was
> Kai> generated by the "ARM Assembler", version 4.0).
> Kai> The .debug_info section just consists of a single debug info entry
> Kai> for each compilation unit, consisting of name, producer, comp_dir,
> Kai> low_pc, high_pc and stmt_list. The .debug_line section contains
> Kai> line statements for the compilation units.
> [...]
> Kai> Any idea what to hunt for ?
> 
> I don't think there's an easy way to debug it.  Offhand I don't know what is
> wrong.  You might try having end_symtab_get_static_block always return a
> block.  It's easier to do this with a newer gdb, this area changed a bit.

What is the relation of DWARF info and (static?) blocks ?
I assume there should be one static block per compilation unit ?

With "newer gdb" I assume you refer to one checked out CVS since 7.5.1 is the latest release ?

Thanks,
Kai