Maximilian Lindner

So far so good. I left one more question about which socket behaviour we’re going to use. I didn’t find time to run the example code yet, but I’ll try...

There are still some stickler warnings. Some seem to be false positives.

`self.exit_status` is set to the second element of the tuple so why can't it be None? Is the status always guaranteed to be set? https://github.com/jtpereyda/boofuzz/blob/d47fe7905013d3f215f36f73f9fd6e06dee39ee5/boofuzz/utils/debugger_thread_simple.py#L155-L156

Ok so with this PR a process exiting with status 0 won't be logged as a crash anymore, will it. Makes sense to me, but will the process monitor automatically...

True. Currently the logging and error handling are closely interwoven. So the process monitor will detect a failure whenever `msg` is not empty. As far as I can tell a...

Sorry for the delay, I just ran some tests with and without the changes from this PR. I'm using a target process that immediately exits with code 0. When I...

Ok, thanks for clearing that up @fouzhe. Correct me if I'm wrong, but from my testing this PR doesn't seem to implement this behaviour. The only thing that changed is...

Did you start `process_monitor.py` on 192.168.3.9? If 192.168.3.9 is your localhost maybe try 127.0.0.1 as the target_ip instead. If you're running the process monitor on a remote machine check if...

Thanks for the input @keisentraut! You do have a point with the API being a little confusing so these changes would be quite some improvement. One problem that as fas...

Sorry for the delayed answer @shoeper. Thanks for reporting. At first sight, I have to idea what's going wrong at the type error but I'll take a closer look at...