Re: GDB 7.7 crashes on LTO-built executable

Eli Zaretskii
2014-02-12T20:11:31Z

> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 12 Feb 2014 13:05:33 -0700
>
> Eli> That's true (I see gobs of calls to that function), but all but one of
> Eli> these calls are from coff_start_symtab, and the argument 'format' is
> Eli> NULL, as expected. There's only one call to record_debugformat from
> Eli> the DWARF 2 reader, the one I described in my original message. This
> Eli> is expected in a single-objfile program, right?

> Yes, I think so, at least if by "single-objfile" you mean "single .o
> file", and not the gdb meaning of the term.

Yes, I meant a single-source file program, and the objfile created
from that source file.

> Eli> I think GDB really doesn't know it have read the DWARF 2 info in this
> Eli> case. I think it uses the COFF information (which includes line
> Eli> table, right?).
>
> I don't know, but all I mean is that if gdb is creating a symtab, then
> there is some code reading some kind of debuginfo to create said symtab;
> and this code must necessarily be specific to some debug format and
> could therefore record it.

Yes, the DWARF 2 debuginfo _is_ recorded, but for a file name that has
nothing to do with the name of the source file from which the program
was compiled.