Hello Axel, > And that fix seems to have been backported in 1.6.2-3 (now in stable, > testing and unstable), see https://bugs.debian.org/1026217
> So this bug report likely can be closed as fixed in libunwind/1.6.2-3
> or (force-) merged with #1026217. (But I'd like to have a second pair
> of eyes agreeing that these two issues are indeed the same before
> merging or closing.)
yes, it was fixed within one week after I opened the bugreport.
Cheers,
Thomas
