
* builds on no_std * fixed std build * nightly fmt on CI * nightly fmt on CI (again) * fmt * no_std build on unix * more mem * added no_std from #212 to gh workflow * more ci, less nightly * clippy * more toolchains? * docu * y u no build * more ci? * next try * fixed dockr * more dockerfile fixes * ondisk corpus fixed * panic:? * ubunutu Co-authored-by: Andrea Fioraldi <andreafioraldi@gmail.com>
8 lines
397 B
Markdown
8 lines
397 B
Markdown
# Baby `no_std`
|
|
|
|
This is a minimalistic example how to create a libafl based fuzzer that works on `no_std` environments like TEEs, Kernels or on barew metal.
|
|
|
|
It runs on a single core until a crash occurs and then calls the panic handler.
|
|
|
|
The tested program is a simple Rust function without any instrumentation.
|
|
For real fuzzing, you will want to add some sort to add coverage or other feedback. |