[PATCH][gdb/breakpoints] Fix longjmp master breakpoint with separate debug info

Tom Tromey tom@tromey.com
Thu Jan 28 20:07:18 GMT 2021


Tom> [ BTW, I think separate_debug_iterator / separate_debug_range is a bit
Tom> of a misnomer, if it iterates over the parent obj first.  It iterates
Tom> over all the objects that could contain debug information, also if
Tom> there's no separate debug info to begin with, f.i. if the parent object
Tom> is unstripped and contains all the debug info.

Tom> So perhaps debug_objfile_iterator / debug_objfile_range is more
Tom> appropriate ? ]

Yeah, now that you point it out, I agree that the current name seems a
bit off.

debug_objfile_* seems a little generic though.

What about maybe 'all_related_objfiles', the idea being that you pass in
an objfile and it iterates over all the "related" ones -- both it and
the separate debug files?

Tom


More information about the Gdb-patches mailing list