New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 699482 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in google_breakpad::MinidumpModule::debug_file

Project Member Reported by ClusterFuzz, Mar 8 2017

Issue description

Cc: mmoroz@chromium.org mummare...@chromium.org ivanpe@chromium.org wfh@chromium.org
Components: Internals>CrashReporting
Labels: Test-Predator-Wrong M-59
Could someone please take a look?
Thank you
Owner: jperaza@chromium.org
Status: Assigned (was: Untriaged)
Based on above comment #2, changed the status to assigned.
Project Member

Comment 4 by ClusterFuzz, Mar 25 2017

ClusterFuzz has detected this issue as fixed in range 459428:459440.

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

Fuzzer: afl_minidump_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  google_breakpad::MinidumpModule::debug_file
  google_breakpad::MinidumpModule::debug_file
  BasicCodeModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=420217:420295
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=459428:459440

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97ys3vSGgBDajYabKeCm_9GGTf6t3Yh0fjs33Zm78QfoeZXjdqeCENHbs7GW7W_i2rLIBLfMhWfwkzXt1AglpKPWCke2eSpFD82lh8sSUOrDMC_XAPXP64ugFvB6eY6VmqLht8bvj5UEUb2b9JK8VK_7T3RFB9hMG22tDZeuMcTCf4XdjtEIRRuDRVLuOm58ElmG6M3bkqxmTwlnPKxGW-zwNhzazGRNPkaq_HioZGIvoQTeD5ukjk4sKiGVFJY2ScJQk7Y4h8lwctcdChQq11nU7yjLgvnXhcJKHkgvWNhDYW3bVh1cMeOGQ_2AqMPR-JQGdJ42agKNZs84BWwyPKdHoNPpqw-R4wcpx3u7o8iZroLU2g?testcase_id=5012858636337152


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.
Project Member

Comment 5 by ClusterFuzz, Mar 25 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5012858636337152 is verified as fixed, so closing issue.

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

Sign in to add a comment