diff options
| author | van Hauser <vh@thc.org> | 2024-10-30 13:20:48 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-30 13:20:48 +0100 |
| commit | d0587a3ac46b1652b1b51b3253c9833d0ea06a13 (patch) | |
| tree | f5d907aafec2fdfe4abca67f8357e9cb1b62d5f4 /docs/env_variables.md | |
| parent | 78b7e14c73baacf1d88b3c03955e78f5080d17ba (diff) | |
| parent | d1fd072b793cba16c28249abefe73ecb7feae4f2 (diff) | |
| download | afl++-d0587a3ac46b1652b1b51b3253c9833d0ea06a13.tar.gz | |
Merge pull request #2226 from AFLplusplus/dev
push to stable
Diffstat (limited to 'docs/env_variables.md')
| -rw-r--r-- | docs/env_variables.md | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/docs/env_variables.md b/docs/env_variables.md index 3db46b36..d1edb6fd 100644 --- a/docs/env_variables.md +++ b/docs/env_variables.md @@ -64,6 +64,9 @@ fairly broad use of environment variables instead: optimizations, set `AFL_DONT_OPTIMIZE`. However, if `-O...` and/or `-fno-unroll-loops` are set, these are not overridden. + - The optimization level can also be set with `AFL_OPT_LEVEL`, e.g. + `AFL_OPT_LEVEL=z` for `-Oz`, default is `3` + - Setting `AFL_HARDEN` automatically adds code hardening options when invoking the downstream compiler. This currently includes `-D_FORTIFY_SOURCE=2` and `-fstack-protector-all`. The setting is useful for catching non-crashing @@ -323,6 +326,11 @@ mode. [instrumentation/README.instrument_list.md](../instrumentation/README.instrument_list.md) for more information. + Setting `AFL_GCC_DISABLE_VERSION_CHECK=1` will disable the GCC plugin + version check if the target GCC plugin differs from the system-installed + version, resolving issues caused by version mismatches between GCC and + the plugin. + Setting `AFL_GCC_OUT_OF_LINE=1` will instruct afl-gcc-fast to instrument the code with calls to an injected subroutine instead of the much more efficient inline instrumentation. @@ -424,9 +432,8 @@ checks or alter some of the more exotic semantics of the tool: types of automated jobs. - `AFL_EXIT_WHEN_DONE` causes afl-fuzz to terminate when all existing paths - have been fuzzed and there were no new finds for a while. This would be - normally indicated by the cycle counter in the UI turning green. May be - convenient for some types of automated jobs. + have been fuzzed and there were no new finds for a while. This is basically + when the fuzzing state says `state: finished` - Setting `AFL_EXPAND_HAVOC_NOW` will start in the extended havoc mode that includes costly mutations. afl-fuzz automatically enables this mode when |