[Bug symtab/29561] [gdb/symtab] During symbol reading: file index out of range

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29561

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
With bisect narrowing in on a window of 17 commits, my bet is on:
...
commit 6d263fe46e00afd8af3d609c1afd71d05eaf745e
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Jan 13 09:48:18 2022 -0700

    Avoid bad breakpoints with --gc-sections

    We found a case where --gc-sections can cause gdb to set an invalid
    breakpoint.  In the included test case, gdb will set a breakpoint with
    two locations, one of which is 0x0.

    The code in lnp_state_machine::check_line_address is intended to
    filter out this sort of problem, but in this case, the entire CU is
    empty, causing unrelocated_lowpc==0x0 -- which circumvents the check.

    It seems to me that if a CU is empty like this, then it is ok to
    simply ignore the line table, as there won't be any locations anyway.
...

Indeed the line table is empty for the CU, but the file table is not.

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