r1viollet

So the unwind_c was essentially to try and investigate the issue. You can remove the build.rs (and everything else that relates to the C reproducer) to focus on the example...

I think [this issue](https://github.com/rust-lang/rust/issues/134592) explains the unwinding failure and has a good example using std functions.

So the summary of the issue is that: - backtrace-rs does not explicitly use libunwind APIs (hence we do not have access to the step API). It would be hard...

Using the context from the signal handler is indeed the correct solution. I get correct unwinding (obviously without the signal frames). ``` USE_CONTEXT=1 ./target-alpine-full/debug/unwind_c ``` I'll leave the example if...