Detect undefined behavior in Rust with Miri and sanitizers.
npx skills add https://github.com/po4yka/RIPDPI --skill rust-sanitizers-miri-po4yka
Please help me install this Agent Skill. Skill: rust-sanitizers-miri Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/rust-sanitizers-miri Command: npx skills add https://github.com/po4yka/RIPDPI --skill rust-sanitizers-miri-po4yka
Rust safety validation is essential to catch undefined behavior, use-after-free, and memory-safety issues in unsafe Rust and FFI code; this skill provides a guided approach using Miri, sanitizers, and Android-specific tools to improve reliability.
Install nightly Rust, enable Miri, and run cargo +nightly miri test to verify undefined behavior in unsafe Rust.
High-intent search queries and answers about installing and using this skill.
Detect undefined behavior in unsafe Rust by running Miri to identify memory-safety issues like use-after-free at FFI boundaries. Applying Miri to unsafe blocks and native bindings catches runtime violations standard compilation misses.
The best way to test JNI bindings under Miri is to implement FFI stubs that safely simulate native code interactions. This prevents crashes by isolating Rust safety validation from external C dependencies during execution.
Yes, you can validate Android builds by combining Miri for undefined behavior detection with HWASan or MTE configurations. This provides documentation on applying on-device sanitizers for safe production builds on Android targets.
Configure MIRIFLAGS and RUSTFLAGS by setting environment variables in your CI templates to enable ASan, TSan, and MSan via Rust toolchains. This establishes repeatable validation pipelines for local testing and automated checks.
Miri works across Rust projects but is essential for those with unsafe blocks and FFI integrations. It specifically targets safety gaps in native bindings and JNI code where undefined behavior and memory issues are most likely.
Miri fails on direct FFI calls because it cannot execute external native code, requiring FFI stubs to bypass this limitation. Users must mock C library interactions to complete Rust safety validation without aborting.
d-o-hubDiagnose runtime issues in Rust async code with Tokio, Turso, and redb.
flexisuite-orgAnalyze unsafe Rust code for FFI and memory safety risks.
multicamInterpret ASan, UBSan, and TSan outputs to identify memory safety violations and data races.
mohitmishra786Validate Rust code for memory safety and undefined behavior with Miri.
