alan
Adds initial support for emitting out a backtrace after a forked DeepState test throws some type of signal using `--verbose_crash_trace`. The output for a buffer overflow/memory corruption example looks as...
As we approach integrating type hints and checking with mypy (https://github.com/trailofbits/deepstate/issues/260 and https://github.com/trailofbits/deepstate/pull/268) and other fun static checking stuff into the dev cycle, it would also be nice to have...
When running test cases against a harness, whether before dynamic analysis execution or after, it may be possible that undefined behavior occurs for the input, and may not be entirely...
Compiling converted-over harnesses that intake a lot of dependencies and may already be apart of a complicated build system does not work entirely well with `--compile_test`, as it only provides...
Since we support much more modern Python 3.x builds, we should use static type checking with our Python codebases. By making our types explicit and more absolute, this should not...
With a refactored frontend API we are now able to instantiate frontend objects using `Frontend.init_fuzzer()`, which takes advantage of `setattr()` to set object attributes from a `dict`. We should take...
Coverage is a good secondary metric besides actual bugs/crashes discovered, as it can provide insight on which uncovered parts of source our analysis tools may need to be used on....
We can replay a test case as so: ```bash $ cargo fuzz run fuzz/artifacts/target/some_input # ... more explicitly: $ cargo fuzz run fuzz/artifacts/target/some_input -- -runs=1 ``` A UX enhancement that...
I made a mistake in forgetting that mangled C++ symbol names start with `_`, and thus analysis on C++ binaries will ignore them altogether. While this has been since fixed,...