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

Issue 734304 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in google_breakpad::PrintStackMachineReadable

Project Member Reported by ClusterFuzz, Jun 17 2017

Issue description

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

Fuzzer: libFuzzer_minidump_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900007d0d
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

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


Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs M-61
Owner: wfh@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "minidump_fuzzer.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/dee978f1ee27b272aeebdc75cecc1ed4f8148eb6

@wfh -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by wfh@chromium.org, Jun 19 2017

Cc: mark@chromium.org
Status: WontFix (was: Assigned)
looks like this is WAI it's hitting an assert on an empty codefile.
Project Member

Comment 3 by ClusterFuzz, Jul 14 2017

Labels: Needs-Feedback
ClusterFuzz testcase 6565735953596416 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
Cc: kkaluri@chromium.org
 Issue 743309  has been merged into this issue.

Sign in to add a comment