From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8772D3858C5F; Thu, 16 Feb 2023 11:36:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8772D3858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676547368; bh=TjbNBoN71kAe9Gtev4HekcWeCO87DQ4DWjCuya5QwQo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Qt26pbM4WkgcDfj5Fdv2FOlaJTSLrKEDWRJnRaKd7QKrlkynsaC+Icqg9c4lmB0/J YxNu6NYtxZ8J8qcHjJpYAXSt/PMWpADnw7Cyj4BPhrkA+YcMf2XqFACscsNTd8qbuZ hBy43mnaZiADsE3L81SNOb03q9mLw2MAuIwO5gSc= From: "petelomax at ymail dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30020] segfault in ld-linux after aug 2022 Date: Thu, 16 Feb 2023 11:36:07 +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: petelomax at ymail dot com 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: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30020 --- Comment #9 from Pete Lomax --- Therein lies the nub. I would love to "fix the bogus binary", but have no i= dea what that segfault actually means, "for some reason" just isn't quite enoug= h. 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-linux first (and the fact that way still works proves at least to me there is not= hing fundamentally wrong with that binary anyway). What I an really here for is to find out what precisely changed in August 2= 022 and what precisely can I do about it. --=20 You are receiving this mail because: You are on the CC list for the bug.=