about summary refs log tree commit diff
path: root/docs/env_variables.md
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2022-02-28 17:42:40 +0100
committerGitHub <noreply@github.com>2022-02-28 17:42:40 +0100
commitd22532d8d3a2b43c9ac9115e31725c874e49fa3e (patch)
tree7786fd479f6b2e119f9f4d1694a4c4e12c656bfd /docs/env_variables.md
parent9b799aedddbd65d6176c838c74385ce3f59c1acb (diff)
parentcd02f635db6d7bd08db11622c4dd7e7ac0889cfe (diff)
downloadafl++-d22532d8d3a2b43c9ac9115e31725c874e49fa3e.tar.gz
Merge pull request #1340 from AFLplusplus/dev
Dev
Diffstat (limited to 'docs/env_variables.md')
-rw-r--r--docs/env_variables.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/env_variables.md b/docs/env_variables.md
index 4626a9b6..edd57fb6 100644
--- a/docs/env_variables.md
+++ b/docs/env_variables.md
@@ -518,7 +518,12 @@ checks or alter some of the more exotic semantics of the tool:
     the target binary. Example: `AFL_TARGET_ENV="VAR1=1 VAR2='a b c'" afl-fuzz
     ... `. This exists mostly for things like `LD_LIBRARY_PATH` but it would
     theoretically allow fuzzing of AFL++ itself (with 'target' AFL++ using some
-    AFL_ vars that would disrupt work of 'fuzzer' AFL++).
+    AFL_ vars that would disrupt work of 'fuzzer' AFL++). Note that when using
+    QEMU mode, the `AFL_TARGET_ENV` environment variables will apply to QEMU, as
+    well as the target binary. Therefore, in this case, you might want to use
+    QEMU's `QEMU_SET_ENV` environment variable (see QEMU's documentation because
+    the format is different from `AFL_TARGET_ENV`) to apply the environment
+    variables to the target and not QEMU.
 
   - `AFL_TESTCACHE_SIZE` allows you to override the size of `#define
     TESTCASE_CACHE` in config.h. Recommended values are 50-250MB - or more if