-
Notifications
You must be signed in to change notification settings - Fork 164
Description
I'm trying to add fuzz tests to an existing code base that has a dependency on a native C DLL that I call via P/Invoke, and I'm getting an intermittent crash in that native library I'm trying to get to the bottom of.
However, because the test process crashes I'm not getting any indication of what the seed was to try and reliably reproduce the sequence of events/inputs that causes the crash because the code doesn't get as far as a failed assertion.
It doesn't seem to be quite as simple as "input A make function B crash" as from some manual logging it appears that which test/function is crashing the process varies, so I think I need to apply the seed to the whole process to get a repro I can reliably debug.
I couldn't see an obvious way to manually access the seed to log it for later re-use - is there a way to do this?