incorporated most of the 2.53b changes

This commit is contained in:
van Hauser
2019-07-26 10:39:14 +02:00
parent 8f4f45c524
commit eea1c6606c
3 changed files with 15 additions and 3 deletions

11
.travis.yml Normal file
View File

@ -0,0 +1,11 @@
language: c
env:
- AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES=1 AFL_NO_UI=1
script:
- make
- ./afl-gcc ./test-instr.c -o test-instr
- mkdir seeds; mkdir out
- echo "" > seeds/nil_seed
- timeout --preserve-status 5s ./afl-fuzz -i seeds -o out/ -- ./test-instr

View File

@ -2,7 +2,7 @@
AFL quick start guide
=====================
You should read docs/README. It's pretty short. If you really can't, here's
You should read docs/README.md - it's pretty short. If you really can't, here's
how to hit the ground running:
1) Compile AFL with 'make'. If build fails, see docs/INSTALL for tips.
@ -17,7 +17,7 @@ how to hit the ground running:
The program must crash properly when a fault is encountered. Watch out for
custom SIGSEGV or SIGABRT handlers and background processes. For tips on
detecting non-crashing flaws, see section 11 in docs/README.
detecting non-crashing flaws, see section 11 in docs/README.md .
3) Compile the program / library to be fuzzed using afl-gcc. A common way to
do this would be:
@ -48,7 +48,7 @@ how to hit the ground running:
That's it. Sit back, relax, and - time permitting - try to skim through the
following files:
- docs/README - A general introduction to AFL,
- docs/README.md - A general introduction to AFL,
- docs/perf_tips.txt - Simple tips on how to fuzz more quickly,
- docs/status_screen.txt - An explanation of the tidbits shown in the UI,
- docs/parallel_fuzzing.txt - Advice on running AFL on multiple cores.

1
docs/README.md Symbolic link
View File

@ -0,0 +1 @@
../README.md