SFT-4385: Don't strip Rust debug information.
What the developer wrote
Authored by Jean-Pierre De Jesus DIAZ
SFT-4385: Don't strip Rust debug information.
* extmod/foundation-rust/Cargo.toml (profile) <release>: Don't strip
debug information.
What changed, and why it matters
This commit changes a Rust build setting so that debug information is no longer removed from the released firmware. On its own, this is a build/debugging convenience change, not a security fix. It does not patch any vulnerability, change runtime behavior, or introduce a known exploit path.
No security action required. If preserving debug symbols in shipped firmware is a concern, ensure the final firmware image still strips or separates symbols before release, or confirm the intended release process with the vendor.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The single-line change sets strip = "none" instead of strip = true in the release profile of extmod/foundation-rust/Cargo.toml. This preserves DWARF/symbol tables in the compiled Rust static library. The change affects only build artifacts and does not alter code logic, memory safety, cryptography, or attack surface. It is a developer-experience change (likely to aid debugging release builds or crash analysis).
Changed components
extmod/foundation-rust/Cargo.toml release profileInspect captured patch +1 / −1
diff --git a/extmod/foundation-rust/Cargo.toml b/extmod/foundation-rust/Cargo.toml
index 3d3e631..aaad751 100644
--- a/extmod/foundation-rust/Cargo.toml
+++ b/extmod/foundation-rust/Cargo.toml
@@ -80,5 +80,5 @@ crate-type = ["lib", "staticlib"]
lto = "fat"
opt-level = "z"
codegen-units = 1
-strip = true
+strip = "none"
panic = "abort"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.