New issue
Advanced search Search tips

Issue 901845 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Record minidumps on ClusterFuzz when a bug is detected

Project Member Reported by metzman@chromium.org, Nov 5

Issue description

As 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
 
Description: Show this description
Summary: Record minidumps on ClusterFuzz when a bug is detected (was: Record minidumps when on ClusterFuzz when a bug is detected)
Cc: brucedaw...@chromium.org
Owner: metzman@chromium.org
Status: Assigned (was: Untriaged)
Labels: Pri-2
Cc: mascasa@google.com r...@chromium.org
I'll investigate this and then figure out if it should be implemented in ASAN, libFuzzer or ClusterFuzz.
>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