public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <sourceware-bugzilla@sourceware.org>
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 [thread overview]
Message-ID: <bug-29899-131-N2KvouiLKw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29899-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29899
John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #8 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-12-30 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 17:43 [Bug libc/29899] New: " glaubitz at physik dot fu-berlin.de
2022-12-13 17:43 ` [Bug libc/29899] " glaubitz at physik dot fu-berlin.de
2022-12-13 17:43 ` glaubitz at physik dot fu-berlin.de
2022-12-13 19:52 ` hjl.tools at gmail dot com
2022-12-13 20:38 ` glaubitz at physik dot fu-berlin.de
2022-12-13 21:12 ` hjl.tools at gmail dot com
2022-12-13 21:22 ` glaubitz at physik dot fu-berlin.de
2022-12-14 7:45 ` sam at gentoo dot org
2022-12-14 7:53 ` glaubitz at physik dot fu-berlin.de
2022-12-14 16:00 ` hjl.tools at gmail dot com
2022-12-21 10:25 ` glaubitz at physik dot fu-berlin.de
2022-12-30 14:35 ` glaubitz at physik dot fu-berlin.de [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29899-131-N2KvouiLKw@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).