This bug was fixed in the package glibc - 2.33-0ubuntu2
---
glibc (2.33-0ubuntu2) hirsute; urgency=medium
* debian/patches/all/local-ldd.diff: Adjust extra safety check
for changed ld-linux.so return value. LP: #1914860.
-- Matthias Klose Sat, 06 Feb 2021 13:32:05 +0100
**
It seems there may be a kernel-side fix:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-January/223199.html
I've committed XFAIL-ing the test for now, to be landed in Hirsute
this/next week.
** Changed in: glibc (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: linux (Ubu
** Changed in: glibc
Status: New => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907298
Title:
glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8
To manage notifications ab
Launchpad has imported 2 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=27223.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://h
Since sigcontextinfo is used internally by glibc only for nice segfault
handling the regression I think it is ok to just XFAIL the test or
adjust sigcontext_get_pc implementation to post-5.10 behaviour, but
upstream may have a different opinion.
** Bug watch added: Sourceware.org Bugzilla #27223
OK, I'll XFAIL this test on ppc64el in next upload, in ~2 weeks.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907298
Title:
glibc 2.3
Reverting "powerpc/64/signal: Balance return predictor stack in signal
trampoline" gets the test passing, so that does appear to be the cause.
I'm not sure what needs to happen here to resolve the test failure
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Looking through powerpc changes between Linux 5.8 and 5.10, I see a
handful of changes to signal-related code. This in particular jumps out
as potentially affecting the register state for signal handling:
commit 0138ba5783ae0dcc799ad401a1e8ac8333790df9
Author: Nicholas Piggin
Date: Mon May 11 2
