From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8F9533858CDA; Fri, 30 Dec 2022 14:35:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F9533858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672410937; bh=kwfTgmDfzFFoSJjwhALB8OdE7RfyL1TNX1PwsWmftCA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nWrbcx32lCbNrbKS4kaxZI17CG2lWyKEFDeNWzD7Oo9sfg1lkghvdQnlIxiQTS5/k 9DYIT4HuJb8isYSdLPJ/1uMXCRAo3bNpfKX4OttbOwEXgAEbb1CDZYGRKAqpYH2WtZ O1RqGGpN8623mpKmXm7qaeCnli9WyQDoyXNpfcg0= From: "glaubitz at physik dot fu-berlin.de" To: glibc-bugs@sourceware.org Subject: [Bug libc/29899] Fix for bz#20305 broke glibc on alpha-linux-gnu Date: Fri, 30 Dec 2022 14:35:36 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.34 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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=3D29899 John Paul Adrian Glaubitz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #8 from John Paul Adrian Glaubitz --- After discussing this issue with Adhemveral, it turns out that my testing method was incorrect and the segfault was a result of mixing ld.so and libc= .so from different glibc builds which, of course, doesn't work. Closing this issue although the original problem may still exist. It affects statically linked programs only, however. --=20 You are receiving this mail because: You are on the CC list for the bug.=