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 34D303858D38; Thu, 27 Apr 2023 07:03:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 34D303858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1682579018;
	bh=p6pqmWBedOuhTvi8giV4CxS5OpNKTzq0WQcVWWsFwmg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=qmgzeZ3JVHH/wa/Cw1uL3z5Skbxng1sXiVJuYCFb3Qfypmy/NP/7YD3DadY4s2Rbl
	 G66E7jA9EXl3WYuBkRpjEOcxk3ECgnWAZFtVJpWa7WlJlNgwZr4Ey/GWua6q/O1/ps
	 Ps8kYaOmfCY5Z6avXwki8dTCUjDBDuSLHfDuPbww=
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/109634] Linking Imagick for PHP compiles fine but gives
 segfault caused by libgomp on runtime
Date: Thu, 27 Apr 2023 07:03:37 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 12.2.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
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: cc
Message-ID: <bug-109634-4-FWbxlTmpPQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109634-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109634-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=3D109634

Alexander Monakov <amonakov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amonakov at gcc dot gnu.org

--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
I remember Glibc used to issue a readable diagnostic in that case ("cannot
allocate memory in static TLS block"). Worth reporting to Glibc if that part
regressed and the diagnostic is no longer available (at least I don't see i=
t in
the linked Github issue).

What is actually happening here? Valgrind catches a null pointer dereferenc=
e,
but where is that null coming from? Is the dynamic linker invoking construc=
tors
with TLS pointer set to null, instead of aborting?=