Question 1

How do I set up cargo-call-stack for my embedded Rust project?

Accepted Answer

Install via `cargo install cargo-call-stack` and add rust-src with rustup nightly. Configure fat LTO in your Cargo.toml release profile, as detailed in the README, to enable proper analysis.

Question 2

cargo-call-stack vs. manual stack analysis in Rust?

Accepted Answer

cargo-call-stack automates static analysis without runtime overhead, unlike manual methods which may involve instrumentation or guesswork. However, it's less accurate for programs with indirect calls compared to dynamic analysis tools.

Question 3

Why does cargo-call-stack give warnings about inline assembly?

Accepted Answer

LLVM's stack analysis ignores inline assembly, so cargo-call-stack uses its own machine code analysis for ARM Cortex-M. Warnings indicate assumptions made, which can affect accuracy on other architectures.

Question 4

Can cargo-call-stack handle exceptions or interrupts in embedded systems?

Accepted Answer

Hardware exceptions appear as disconnected nodes in call graphs, and the tool cannot compute whole-program stack usage when exceptions are present, limiting its completeness for real-time systems.

Question 5

What should I do if cargo-call-stack breaks after a Rust update?

Accepted Answer

Check the last tested nightly version in the README and consider pinning your toolchain. The project acknowledges it could stop working anytime due to reliance on experimental features.

Question 6

Is cargo-call-stack suitable for analyzing recursion in embedded code?

Accepted Answer

Yes, it can detect cycles in call graphs and compute stack bounds where recursion is bounded, but accuracy depends on direct calls and may not handle all recursive patterns.

cargo-call-stack

What is cargo-call-stack?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions