Record minidumps on ClusterFuzz when a bug is detected |
|||||
Issue descriptionAs requested by brucedawson@ in crbug.com/897872#c34 Record minidumps when a bug is detected. Optionally have these be full minidumps. Optionally record these (and the relevant PDB and PE files) when a bug is found by clusterfuzz so that it can be investigated without even having to reproduce it. Recording a call stack should not be the only option. Ideally we should check an environment variable and if it is set then save a full or partial minidump. It's really easy: https://docs.microsoft.com/en-us/windows/desktop/api/minidumpapiset/nf-minidumpapiset-minidumpwritedump
,
Nov 5
,
Nov 5
,
Nov 5
,
Nov 5
I'll investigate this and then figure out if it should be implemented in ASAN, libFuzzer or ClusterFuzz.
,
Nov 5
>Optionally have these be full minidumps. I think this might be a problem with ASAN since it uses tons of virtual memory I've heard the dumps can be too large. We may have to go with minidumps. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by metzman@chromium.org
, Nov 5