Unwinding the Stack the Hard Way

1. rust-minidump

   1 3 437 8.7 Rust

   Type definitions, parsing, and analysis for the minidump file format.

   

   Generally what we do when we fall back to scanning depends on the architecture. For x86 you can find the logic here: https://github.com/rust-minidump/rust-minidump/blob/77638ab7...

   Since we do post-hoc stack walking our ability to actually look at the assembly is limited. In most cases where we have no CFI we also do not have the binary to begin with, so we're in random memory land.

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. ClickHouse

   2 232 38,466 10.0 C++

   ClickHouse® is a real-time analytics database management system

   

   We have implemented asynchronous signal-safe in-process stack unwinding for always-on profiler in ClickHouse: https://clickhouse.com/docs/en/operations/optimizing-perform...

   The downside - it required many patches to LLVM's libunwind, and not all of them are accepted yet: https://bugs.llvm.org/show_bug.cgi?id=48186

   ClickHouse source code: https://github.com/ClickHouse/ClickHouse

4. tock

   3 33 5,573 9.9 Rust

   A secure embedded operating system for microcontrollers

   

   Yeah, and I like I mentioned in the earlier comment, omitting the frame pointer reduces code size by 10% on RISC-V targets, which is huge when dealing with embedded flash: https://github.com/tock/tock/pull/1660

Suggest a related project