about summary refs log tree commit diff
path: root/docs
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2020-09-06 15:12:23 +0200
committervan Hauser <vh@thc.org>2020-09-06 15:12:23 +0200
commit7bcbfd48e54eba5a99d05b04f4f3d6bea29cde80 (patch)
treedcc7a78b70c3313d77814249dbf9c96bf30688f5 /docs
parent06ac2850c54412ee8897361f8ff05a649a716b30 (diff)
downloadafl++-7bcbfd48e54eba5a99d05b04f4f3d6bea29cde80.tar.gz
update ideas
Diffstat (limited to 'docs')
-rw-r--r--docs/ideas.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/ideas.md b/docs/ideas.md
index a5d40963..aaa3eed1 100644
--- a/docs/ideas.md
+++ b/docs/ideas.md
@@ -3,6 +3,19 @@
 In the following, we describe a variety of ideas that could be implemented
 for future AFL++ versions.
 
+## Analysis software
+
+Currently analysis is done by using afl-plot, which is rather outdated.
+A GTK or browser tool to create run-time analysis based on fuzzer_stats,
+queue/id* information and plot_data that allows for zooming in and out,
+changing min/max display values etc. and doing that for a single run,
+different runs and campaigns vs campaigns.
+Interesting values are execs, and execs/s, edges discovered (total, when
+each edge was discovered and which other fuzzer share finding that edge),
+test cases executed.
+It should be clickable which value is X and Y axis, zoom factor, log scaling
+on-off, etc.
+
 ## WASM Instrumentation
 
 Currently, AFL++ can be used for source code fuzzing and traditional binaries.