Crates.io | libafl_bolts |
lib.rs | libafl_bolts |
version | |
source | src |
created_at | 2023-08-28 15:15:14.7239 |
updated_at | 2024-12-02 21:46:31.377216 |
description | Low-level bolts to create fuzzers and so much more |
homepage | |
repository | https://github.com/AFLplusplus/LibAFL/ |
max_upload_size | |
id | 957096 |
Cargo.toml error: | TOML parse error at line 22, column 1 | 22 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
The libafl_bolts
crate exposes a lot of low-level features of LibAFL for projects that are unrelated to fuzzing, or just fuzzers completely different to LibAFL.
Some cross-platform things in bolts include (but are not limited to):
core_affinity
that can be used to get core information and bind processes to coresfork
LibAFL_bolts is written and maintained by
For bugs, feel free to open issues or contact us directly. Thank you for your support. <3
Even though we will gladly assist you in finishing up your PR, try to
cfg
s)cargo nightly fmt
on your code before pushingcargo clippy --all
or ./clippy.sh
cargo build --no-default-features
to check for no_std
compatibility (and possibly add #[cfg(feature = "std")]
) to hide parts of your code.Some of the parts in this list may be hard, don't be afraid to open a PR if you cannot fix them by yourself, so we can help.