alan

Sure! There is some initial work I was playing around with on the `py3-static-types` branch. Feel free to pull and work off what has been done in `bin/deepstate/frontend/frontend.py` for the...

It's up to you to determine what should be integrated with static checking, since there's actually quite a lot of Python code that has evolved in the repo. However, some...

I think having explicit type hints everywhere (even in the most obvious places) would work well with a static checker in regards to finding any low-hanging type-related issues that may...

Yes! Did a pass of type checking with mypy on our core frontend API, in anticipation of refactoring and adding new features. Feel free to approach this on any of...

Stack unwinding and backtrace becomes tricky and a little intrusive / not super security conscious when involving forked processes during execution, since it involves using `ptrace`, most likely through `libunwind`'s...

It seems like a lot of fuzzers work similarly, and that a lot of the front-ends would end up looking almost the same. Would it be a good idea to...

For example, maybe something like this: ``` $ deepstate-angora --compile harness.c ``` The front-end finds the path to `angora-clang`, (or `angora-clang++` for `.cpp`) and compiles accordingly. A corresponding method in...

To some extent, we try to do this with `DeepState_InputPath`, seen [here](https://github.com/trailofbits/deepstate/issues/238), which enables us to parse out a filename rather than read it out completely, and can be useful...

Cool recommendation! One thing that kind of works towards improving the workflow aspect of the framework is with how we manage parsing configurations by including a reserved `manifest` section, which...

Looking at the stack trace, the culprit function is `BNSettingsGetStringList`. How does your settings configuration look like for fuzzable? Are they the default configured parameters? I've tried setting mine to...