From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 562523854551; Fri, 18 Nov 2022 17:32:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 562523854551
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1668792777;
	bh=Ije5afd+MjbpTWlRp6ihqFiEHaHuMpgiGoqwoKSNTD8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=TedEc/tYkl2AagGY7JhdJSfmEV4Rh/qkHHNtleiDNwAkNHjnhiVLaebgHZb5ltvqF
	 Ew6+uUL438yy0sJOzDkoVspo0e/8kJCA8R8TlOqdTGRyqoCV1LKVIkDy2UXlzyGsBl
	 OobD5XwWq+bHegFugJTxG9G/5WvLStEtpqXorZQM=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [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)
Date: Fri, 18 Nov 2022 17:32:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: symtab
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29805-4717-sTQlOIOmtw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29805-4717@http.sourceware.org/bugzilla/>
References: <bug-29805-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

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

--- 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.
>=20
> 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 | g=
rep
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" =3D true ]; then
        echo "$myname: dwz file $dwz_file missing."
        exit 1
     fi
+    rm -f "$dwz_file"
 fi

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

The same assert triggers in the same test-case.

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