Re: [PATCH] [gdb/symtab] Add set/show always-read-ctf on/off

[Tom Tromey <tom@tromey.com>]

>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:

Tom> The setting is off by default, preserving current behaviour.

Tom> A bit of background on the relevance of reading order: the formats have a
Tom> priority relationship between them, where reading earlier means lower
Tom> priority.  By reading the format with the most detail last, we ensure it has
Tom> the highest priority, which makes sure that in case there is overlapping info,
Tom> the most detailed info is found.  This explains the current reading order of
Tom> mdebug, stabs and dwarf2.

Tom> Add the unconditional reading of ctf before dwarf2, because it's less detailed
Tom> than dwarf2.  The conditional reading of ctf is still done after the attempt to
Tom> read dwarf2, necessarily so because we only know whether there's dwarf2 after
Tom> we've tried to read it.

I'm sorry I didn't comment on the earlier thread.

I wonder if the current behavior is important.  Why not just always read
all the debug info that gdb supports?  This is how stabs+DWARF works and
it makes a certain kind of sense -- due to separate compilation, you can
wind up with an aggregate object (like an executable) where each
individual part was made differently.

That is, instead of the option, why not make it unconditional?

Tom