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 E01C83858C78; Thu, 16 Feb 2023 11:59:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E01C83858C78
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1676548755;
	bh=zOKxXK7+1pOOb4KznNNW/RCmvIJBNCejHOFgyTM8d6Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=RKEsnaHbLhPpS8em5BtXTX7XRvDANC8pV+pz7uqf1/go6cHREk0PnHTtihFoCjDAO
	 PkLTpCqJ/TcHVSzysCnyHMXNs7mSkRJjbEbtl627B6/g2uGcKkuJ5o4BA9Kp1t1Obk
	 bJMd3KVM4i5BzybaMiHbVL5VUeuwQE7t43CFfGzs=
From: "adhemerval.zanella at linaro dot org"
 <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30020] segfault in ld-linux after aug 2022
Date: Thu, 16 Feb 2023 11:59:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adhemerval.zanella at linaro dot org
X-Bugzilla-Status: UNCONFIRMED
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-30020-131-YMtv2bUbnS@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30020-131@http.sourceware.org/bugzilla/>
References: <bug-30020-131@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: <glibc-bugs.sourceware.org>

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

--- Comment #10 from Adhemerval Zanella <adhemerval.zanella at linaro dot o=
rg> ---
(In reply to Pete Lomax from comment #9)
> Therein lies the nub. I would love to "fix the bogus binary", but have no
> idea what that segfault actually means, "for some reason" just isn't quite
> enough.
>=20
> I have already patched the binary to appease readelf, as best I can, but =
it
> does not fix the problem, and further also fubars the running of it ld-li=
nux
> first (and the fact that way still works proves at least to me there is
> nothing fundamentally wrong with that binary anyway).
>=20
> What I an really here for is to find out what precisely changed in August
> 2022 and what precisely can I do about it.

You can try bisect by rebuilding your binary with -Wl,-dynamic-linker=3D (s=
imilar
to what --enable-hardcoded-path-in-tests) so you don't mess with your syste=
m.
It is quite time-consuming to debug it because patchelf does not work this
binary (and hexedtting is quite tedious), if you could provide a source cod=
e on
how to reproduce it would be immensely better.

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