[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)

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

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> 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.

Hmm, that doesn't seem to be possible because it doesn't have a
.gnu_debugaltlink:
...
$ readelf -S -W libgcc_s.so.1-11.3.0+git1637-150000.1.11.2.x86_64.debug | grep
alt
$
...

But I managed to trigger it by playing with the cc-with-dwz-m board:
...
diff --git a/gdb/contrib/cc-with-tweaks.sh b/gdb/contrib/cc-with-tweaks.sh
index 0ad0091d47a..ce6798c38a8 100755
--- a/gdb/contrib/cc-with-tweaks.sh
+++ b/gdb/contrib/cc-with-tweaks.sh
@@ -247,6 +247,7 @@ elif [ "$want_multi" = true ]; then
        echo "$myname: dwz file $dwz_file missing."
        exit 1
     fi
+    rm -f "$dwz_file"
 fi

 if [ "$want_dwp" = true ]; then
...

The same assert triggers in the same test-case.

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