[Bug symtab/29805] New: [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)

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

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

            Bug ID: 29805
           Summary: [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)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On powerpc64le-linux, I ran into a gdb internal error:
...
(gdb) could not find '.gnu_debugaltlink' file for
/usr/lib/debug/lib64/libgcc_s.so.1-11.3.0+git1637-150000.1.11.2.ppc64le.debug^M
inferior 2^M
[Switching to inferior 2 [process 56507]
(/suse/tdevries/gdb/build/gdb/testsuite/outputs/gdb.threads/access-mem-running-thread-exit/access-mem-running-thread-exit)]^M
[Switching to thread 2.1 (Thread 0x7ffff7ff3d90 (LWP 56507))](running)^M
(gdb) /suse/tdevries/gdb/src/gdb/dwarf2/read.c:7284: internal-error:
create_all_units: Assertion `per_objfile->per_bfd->all_units.empty ()'
failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
----- Backtrace -----^M
FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access mem
(write to global_var, inf=2, iter=1) (GDB internal error)
...

The circumstances are a bit peculiar, I messed around with debug packages and
broke the .gnu_debugaltlink for libgcc_s.so.1.  Still, we shouldn't abort.

I'll try to reproduce on x86_64-linux.

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