flip-link VS cargo-call-stack

Compare flip-link vs cargo-call-stack and see what are their differences.

flip-link

Adds zero-cost stack overflow protection to your embedded programs (by knurling-rs)

cargo-call-stack

Whole program static stack analysis (by Dirbaio)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
flip-link cargo-call-stack
3 1
232 4
3.9% -
7.2 5.7
17 days ago 3 months ago
Rust Rust
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

flip-link

Posts with mentions or reviews of flip-link. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-14.

cargo-call-stack

Posts with mentions or reviews of cargo-call-stack. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-14.
  • Measuring Stack Usage the Hard Way
    2 projects | news.ycombinator.com | 14 Feb 2024
    At least in Rust, we have `cargo-call-stack` [0] for static analysis, but "worst case stack usage" can be challenging to measure, if you have interrupts (including nested ones at different prios so you have to add them together!), function pointers (including dyn dispatch), or recursion.

    There are ways to annotate and work around this! I'm also from a safety critical background. But there aren't many (any?) OSS tools that do this completely. cargo-call-stack is the closest I've seen.

    [0]: https://github.com/Dirbaio/cargo-call-stack/

    I agree static analysis is preferrable, but it's also not a "just enable the check, duh" easy, sadly, and it's good to know different techniques.

What are some alternatives?

When comparing flip-link and cargo-call-stack you can also consider the following projects:

defmt - Efficient, deferred formatting for logging on embedded systems

awesome-embedded-rust - Curated list of resources for Embedded and Low-level development in the Rust programming language

wg - Coordination repository of the embedded devices Working Group

app-template - Quickly set up a `probe-rs` + `defmt` + `flip-link` embedded project

stm32f7xx-hal - A Rust embedded-hal HAL for all MCUs in the STM32 F7 family

factorio-cheat-sheet - Cheat Sheet for Factorio

rust-raspberrypi-OS-tutorials - :books: Learn to write an embedded OS in Rust :crab:

probe-run - Run embedded programs just like native ones

rustberry-pi-pico - Collection of firmware binaries for Raspberry Pi Pico written in Rust.