ASSERT: !frame->module->code_file().empty() |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6302603760369664 Fuzzer: libFuzzer_minidump_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !frame->module->code_file().empty() google_breakpad::PrintStackMachineReadable google_breakpad::PrintProcessStateMachineReadable Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=510445:510468 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6302603760369664 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jun 5 2018
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jun 5 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d7ebcbcf5f4b8eeec191a1bb8e68d3b67f6d3b8d (Explicitly add signature and header in minidump fuzzer). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Dec 1
ClusterFuzz testcase 6302603760369664 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Jun 5 2018Labels: Test-Predator-Auto-Components