Le mardi 12 novembre 2024 à 15:48 +0100, Vincent Lefevre a écrit : > Hi, > > On 2024-10-11 09:16:26 +0200, Alban Browaeys wrote: > > Upstream in https://github.com/libunwind/libunwind/issues/672 for > > 1.8. > > This is unclear. https://github.com/libunwind/libunwind/issues/672 is > about 1.7.2, and this issue is closed as being fixed in 1.8. > >
It is fixed in https://github.com/libunwind/libunwind/commit/f35c38746d47a5159163ca9e8845a3ac8cf1bc53 that is 1.8.1. As told in the issue the bug is about newer compiler, not a code change. So every release below 1.8.1 is affected. And the current broken debian version is 1.7.2, so I am puzzled by your statement that the fix on this github issue is about 1.7.2 so does not apply to Debian. To me this is perfectly normal that an issue for 1.7.2 is fixed in 1.8.1, I don't understand why you tell "This is unclear". As usual this requires backporting to older a code base ie 1.7.2. As every backport. > > Also gentoo for libunwind 1.8: > > sys-libs/libunwind: Gos-linux.c:302:22: error: passing argument 1 > > of > > ‘_Ux86_sigreturn’ from incompatible pointer type [-Wincompatible- > > pointer-types] > > https://bugs.gentoo.org/918969 > > Ditto, the gentoo bug is about libunwind 1.7.2 and the whiteboard > says: "fixed in 1.8.0". > > So I suppose that the solution is to upgrade to 1.8.1 (version > mentioned on https://tracker.debian.org/pkg/libunwind). > Upgrading to 1.8.1 would fix this bug. If it is doable let's do it. But it might requires a migration of the packages that depends on libunwind-18 (would it be libunwind-19) so I it might not help with these packages depending on libunwind-18. Note that this fix fixes multiple issues at once: " Fix test-async-sig on x86-linux The x86-specific code would often mistakenly advance the cursor through the signal trampoline by misinterpreting what was on the stack, and it just happened to work most of the time. It was wrong, however, and moving the signal trampolive detection up before the DWARF stepping (like it is on other target architectures) should make it do the right thing. This change had the cascade effect of tickling some undefined behaviour in the target architecture-specific unw_resume code, so that got fixed too. " Best, Alban
