From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6DE1D3858D37; Mon, 15 May 2023 06:06:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6DE1D3858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1684130786;
	bh=Kczu9p9TimjLi0SmOQQJwPcY61S/+Y9f2Nk0uGLFnQo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Ahzbw4pIFqYLxe3mvxtxRYCt2b7jm5dEXQMb4ZcOc660mjkXlE67S/GDbnp/Ij4L1
	 l75inQfSA+0FZ3A1kw0vb1ZZiMMHysmOwm19GelnQbuU2oAzYgkF2AS6k4z5e1MlA4
	 1kSgULtfFm+0y/ZqAmomASnKkljn0zfGQZfgD6ok=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/109712] Segmentation fault in linear_search_fdes
Date: Mon, 15 May 2023 06:06:25 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109712-4-6IyGUCWHlC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109712

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Carlos Galvez from comment #6)
> Hi again!
>=20
> I realized there is still one more problem missing, so I suspect the link=
er
> was not the only culprit. It does not segfault, but it gets stuck in an
> infinite loop, once again when mixing exceptions and libcudart_static.a.
>=20
> @Richard you mentioned:
>=20
> > Does libcudart_static.a by chance contain any symbols from the libgcc r=
untime (of an old toolchain)?
>=20
> Do you know how I could verify this? I'm pretty new when it comes to
> troubleshooting these things.
>=20
> My understanding is that libstdc++.so and libgcc_s.so are always backwards
> compatible so using "the latest" ensures you can use the newest features =
and
> also run older built code. Is there a flaw/pitfall in that reasoning?

There were changes to the internal data structures of the unwinder so I
wondered if you somehow managed to mix unwinder parts of different versions.

You probably have a libgcc_eh.a file as part of your GCC install, you could
look for symbols this library provides in the NVIDIA static archives.

> Thanks!=