Embedded code coverage?
⚓ Rust 📅 2025-09-09 👤 surdeus 👁️ 8I'm wondering how RUST supports code coverage in an embedded system with NO Operating system, NO File System, ie: NO_SYS?
I need to do this "in target/in-situ" - because coverage needs to cover drivers that are talking to hardware registers that cannot be reasonably mocked.
Generally, most coverage things create an ABSOLUTLY huge RAM table that gets dumped to a file when the program exits.
Concerns:
(A) I have 32K bytes of RAM not 32MEG of RAM - I cannot support a HUGE ram table.
(B) I do not have a filesystem, nor do I have an RTOS
(C) In order to make it fit - will probably need to separately enable coverage one file at a time then merge the coverage results and produce a final report from all of the other runs.
That's how I've done it with C code..
Anybody have suggestions where to read up on this?
1 post - 1 participant
🏷️ Rust_feed