DeforaNetworks/deepstate
3
0
Fork 0
Code Releases Activity

minor fixes to output improvements, correct README

Browse Source
This commit is contained in:
Alex Groce 2019-01-03 19:22:14 -07:00
parent c58ca9b116
commit 2fbfa652b4
2 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -115,6 +115,15 @@ argument to see all DeepState options.
DeepState consists of a static library, used to write test harnesses, and command-line _executors_ written in Python. At this time, the best documentation is in the [examples](/examples) and in our [paper](https://agroce.github.io/bar18.pdf). A more extensive example, using DeepState and libFuzzer to test a user-mode file system, is available [here](https://github.com/agroce/testfs); in particular the [Tests.cpp](https://github.com/agroce/testfs/blob/master/Tests.cpp) file and CMakeLists.txt show DeepState usage.
## Log Levels
By default, DeepState is not very verbose about testing activity,
other than failing tests. The `--log-level` argument lowers the
threshold for output, with 0 = `DEBUG`, 1 = `TRACE` (output from the
tests, including `printf`s), and 2 = INFO (DeepState messages, the default), 3 = `WARNING`,
4 = `ERROR`, and 5 = `EXTERNAL` (output from other programs such as
libFuzzer), and 6 = `CRITICAL`/`FATAL` messages.
## A Note on Mac OS and Forking
Normally, when running a test for replay or fuzzing, DeepState forks
@ -133,12 +142,7 @@ The fuzzer also takes a `seed` and `timeout` (default of two minutes)
to control the fuzzing. If you want to actually save the test cases
generated, you need to add a `--output_test_dir` arument to tell
DeepState where to put the generated tests. By default fuzzing saves
only failing and crashing tests. One more command line argument that
is particularly useful for fuzzing is the `--log_level` argument,
which controls how much output each test produces. By default, this
is set to show all the logging from your tests, which slows fuzzing,
but setting it to 2 or higher will only show messages produced by
tests failing or crashing.
only failing and crashing tests and only when given an output directory.
Note that while symbolic execution only works on Linux, without a
fairly complex cross-compliation process, the brute force fuzzer works

4
src/include/deepstate/DeepState.h
View File

@ -706,8 +706,8 @@ static int DeepState_RunSavedCasesForTest(struct DeepState_TestInfo *test) {
closedir(dir_fd);
free(test_case_dir);
DeepState_LogFormat(DeepState_LogInfo, "Ran %u tests; %d tests failed",
i, num_failed_tests);
DeepState_LogFormat(DeepState_LogInfo, "Ran %u tests for %s; %d tests failed",
i, test->test_name, num_failed_tests);
return num_failed_tests;
}