From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7236C3857BAE; Tue, 25 Oct 2022 12:01:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7236C3857BAE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666699316; bh=yL1A5adYXAEkHlLq9xqyxrLMLkSnQYn0kH4Dh8guxmI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dOEkkctB6x57qW6zlvaaiq37BKzeMWQGPyMwmVlNVe7kC9zsS3b8gwAXjod0OKnK9 MHfRPbcpkzG6h5+HE9IfTm1qGbf8jyGgFVcXmXBk/ViK5ykuwbwoO69d69UrjoLPx4 CkbodLxLia11SYNHljztThECOQe22dAmmpM7jDGg= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105730] [12/13 Regression] Issue with commit - Allow std::condition_variable waits to be cancelled Date: Tue, 25 Oct 2022 12:01:56 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 12.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105730 --- Comment #3 from Jonathan Wakely --- (In reply to Lance Fredrickson from comment #0) > Thread 2 "ld.lld" received signal SIGSEGV, Segmentation fault. > [Switching to LWP 27688] > 0x42deada0 in > std::condition_variable::wait(std::unique_lock&)@GLIBCXX_3.4.= 11 > () from /mmc/usr/lib/libstdc++.so.6 If ld.lld was built against gcc-12 then why is it linking to the @GLIBCXX_3.4.11 symbol? Does this target support symbol renaming using .symver ?=