Snaipe

I think I'll had a matrix entry to test on Visual Studio 2017, since I remember that VS2017 broke things that previously worked on VS2015, but the main issue remains...

This is something to consider for #204. If we were to implement this, the simplest semantic way would be to simply provide a list of parents to the test. I...

The reason why `--single` was removed is that is was hard to keep the option with the new i/o layer changes (we switched to a nanomsg + protobuf stack) and...

One more thing: I haven't tested it since --single was there, but I think that multi-inferior debugging might still be working. Maybe it'll integrate better with CLion? To set up...

I just tried the multi-inferior setup, and it worked surprisingly well! I've cooked up a small gdb script to help make the initial setup less painful: ```gdb set follow-fork-mode child...

I don't think that's possible right now, and it would be really tricky to properly implement. The reason why is that we'd need to both know if we crashed and...

Yes, this is the same issue. It used to work before the changes to the i/o layer, as the final exit status was used as a final override on the...

There is currently no supported way to do so. Even if you wanted to be really really naughty by changing `criterion_current_test->name` from within the test, the runner would get confused...

log messages are not part of any output report, as we don't store these (and they technically are there for informative purposes, though one can argue about that for e.g....

Do you perhaps have a self-contained .c file that I can just compile and debug on my end? I think BoxFort might be missing some corner-case ASLR there.