On Fri, 15 Nov 2024 at 15:16:04 +0100, Alban Browaeys wrote:
> 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.
This bug report is only about libunwind{8,-dev}, from the
src:libunwind source package, https://github.com/libunwind/libunwind
upstream, currently at version 1.7.2, with various people asking for an
upgrade to the newer upstream version 1.8.1 to fix bugs like this one.
It looks as though the newer upstream version will still be
libunwind.so.8, so no ABI transition (assuming the upstream developers
are handling the ABI correctly) and it can stay as libunwind8.
libunwind-{18,19,...}{,-dev} are a different implementation of similar
functionality, from the src:llvm-toolchain-* family of source packages,
https://www.llvm.org/ upstream, with a version number matching the LLVM
version (currently at 19.1.3). Upgrading src:libunwind shouldn't affect
the contents of those.
I'm not sure whether LLVM libunwind is a fork of this libunwind or an
independent reimplementation, but either way it's out-of-scope for this
bug report.
smcv
