From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2E17E3858D33; Thu, 11 Apr 2024 21:47:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E17E3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712872024; bh=smRDvlbRckPyu3L4SIGCPl/ZANcy14rW0DZJyAKUvfU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qwicFC5tz/pMAWMfHK/9vE/1+OMZ4bWIw2C2kqopRpgbUdDc5fV4RZyQS5a4rz+Mk haSSu2r8t1gAheyfO6xFtA2I0TtOB0/C/CA5T4jqEyeVDgMPXTEIciB/LOizBlPtov 9Ff6l3YWTxU7EjDgvO8GRZTFz2axo4VvKbo+Txws= From: "rjones at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/114699] gcc-go -buildmode=c-shared doesn't use -Wl,-z,nodelete so libraries crash when dlclosed Date: Thu, 11 Apr 2024 21:47:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rjones at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- 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=3D114699 --- Comment #3 from Richard W.M. Jones --- (Edit comment 2: To be clear, that wasn't the thread where the segfault occurred, which was some golang thread, that was the thread that was unmapping the memory at the same time. Using nodelete avoids this by not actually unmapping the code.)=