[Bug symtab/29805] [gdb/symtab] FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access mem (write to global_var, inf=2, iter=1) (GDB internal error)

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

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=05ad0d60341f0933501dc90002da3d4594c30438

commit 05ad0d60341f0933501dc90002da3d4594c30438
Author: Tom de Vries <tdevries@suse.de>
Date:   Sat Nov 26 14:13:06 2022 +0100

    [gdb/symtab] Handle failure to open .gnu_debugaltlink file

    If we instrument cc-with-tweaks.sh to remove the .gnu_debugaltlink file
after
    dwz has created it, with test-case
    gdb.threads/access-mem-running-thread-exit.exp and target board
cc-with-dwz-m
    we run into:
    ...
    (gdb) file access-mem-running-thread-exit^M
    Reading symbols from access-mem-running-thread-exit...^M
    could not find '.gnu_debugaltlink' file for
access-mem-running-thread-exit^M
    ...
    followed a bit later by:
    ...
    (gdb) file access-mem-running-thread-exit^M
    Reading symbols from access-mem-running-thread-exit...^M
    gdb/dwarf2/read.c:7284: internal-error: create_all_units: \
      Assertion `per_objfile->per_bfd->all_units.empty ()' failed.^M
    ...

    The problem is that create_units does not catch the error thrown by
    dwarf2_get_dwz_file.

    Fix this by catching the error and performing the necessary cleanup,
getting
    the same result for the first and second file command.

    PR symtab/29805
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29805

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