Test Predator has given the following results:

Add minidump fuzzer for breakpad. by wfh@chromium.org
Minimum distance between changed lines and stacktrace lines in minidump_fuzzer.cc is 0
Top touched frame is #6 (in minidump_fuzzer.cc)
Changed files BUILD.gn, minidump_fuzzer.cc, minidump_fuzzer.dict, with the same CrashedDirectory(breakpad) as minidump_fuzzer.cc (in frame#6)
Touched files in stacktrace - minidump_fuzzer.cc
Changed files BUILD.gn, minidump_fuzzer.cc, minidump_fuzzer.dict, with the same CrashedComponent(Internals>CrashReporting) as minidump_fuzzer.cc (in frame#6)

@wfh -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.

ClusterFuzz has detected this issue as fixed in range 510445:510468.

Detailed report: https://clusterfuzz.com/testcase?key=5243926134128640

Fuzzer: libFuzzer_minidump_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e90000468e
Crash State:
  google_breakpad::PrintStackMachineReadable
  google_breakpad::PrintProcessStateMachineReadable
  PrintMinidumpProcess
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=416025:416193
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=510445:510468

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5243926134128640

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5243926134128640 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.