public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "debian-alpha@lists.debian.org" <debian-alpha@lists.debian.org>
Cc: gentoo-alpha@lists.gentoo.org, GNU C Library <libc-alpha@sourceware.org>
Subject: Update on the glibc segfault issue on Alpha
Date: Mon, 2 Jan 2023 12:44:40 +0100	[thread overview]
Message-ID: <999879fc-9cb3-1efa-165b-36a5418f2e41@physik.fu-berlin.de> (raw)

Hello!

Just a quick update on the glibc issue we're seeing on Alpha!

My previous bisecting result was wrong and the segfault I ran into was the result
of combining ld.so and libc.so files from different builds by not including all
necessary paths in my LD_LIBRARY_PATH. So, my previously reported bug report was
invalid [1].

However, as can be seen from the build logs, there are still clearly issues with
the testsuite [2]. Further analysis showed that the problem are static binaries
which segfault. Anything dynamically linked, works.

This becomes obvious when building the glibc Debian package manually with the testsuite
disabled and then installing these packages inside a test chroot. While the libc-bin
package is being configured, ldconfig is run - a statically linked binary - and crashes
with a segfault.

Adhemerval from glibc upstream is aware of the problem but he has not found yet a solution
to this issue as it needs to be debugged further. I will try to bisect which particular
introduced the regression and file a new upstream bug report.

During our discussion, Adhemerval pointed out that this change [3] might be the culprit
but I have not been able to verify this yet.

Adrian

> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=29899
> [2] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=alpha&ver=2.36-6&stamp=1669706903&raw=0
> [3] https://sourceware.org/pipermail/glibc-cvs/2020q2/069444.html

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

             reply	other threads:[~2023-01-02 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 11:44 John Paul Adrian Glaubitz [this message]
2023-01-02 17:37 ` John Paul Adrian Glaubitz
2023-01-03 12:09   ` Adhemerval Zanella Netto
2023-01-03 13:29     ` Florian Weimer
2023-01-03 13:47       ` Adhemerval Zanella Netto
2023-01-04  9:25     ` John Paul Adrian Glaubitz
2023-01-04 12:00       ` Adhemerval Zanella Netto
2023-01-05 11:25         ` John Paul Adrian Glaubitz

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=999879fc-9cb3-1efa-165b-36a5418f2e41@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-alpha@lists.debian.org \
    --cc=gentoo-alpha@lists.gentoo.org \
    --cc=libc-alpha@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).