New issue
Advanced search Search tips

Issue 773183 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Abrt in /usr/lib/libc++abi.dylib:x86_64

Project Member Reported by ClusterFuzz, Oct 10 2017

Issue description

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Abrt
Crash Address: 0x7fff8e94bf06
Crash State:
  /usr/lib/libc++abi.dylib:x86_64
  /usr/lib/libc++abi.dylib:x86_64
  _objc_terminate
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=459180:459211

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 10 2017

Components: Internals>Plugins>PDF
Labels: Test-Predator-AutoComponents
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Oct 10 2017

Labels: Test-Predator-AutoOwner
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/034ca9381180401b9b25eac088babf7fdae847d8 (Add XFA pdfium fuzzer).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Owner: rharrison@chromium.org
Project Member

Comment 4 by ClusterFuzz, Oct 19 2017

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=4987882547970048.

Comment 5 by mmoroz@chromium.org, Oct 24 2017

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.
Status: Started (was: Assigned)
Project Member

Comment 7 by bugdroid1@chromium.org, Nov 1 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/98b579c1f5a358508dc0cca855c687ed51ccd6f7

commit 98b579c1f5a358508dc0cca855c687ed51ccd6f7
Author: Ryan Harrison <rharrison@chromium.org>
Date: Wed Nov 01 21:54:06 2017

Fetch executable path for Mac in helper

The current implementation for Mac crashes, since /proc/ doesn't exist and thus
the path being searched for. This leads to attempting to create a string of
length 0.

This adds in Mac specific logic for fetching this information.

BUG= chromium:773183 

Change-Id: I57bc2530ee79a51c0caad42ec31f640f73c7a7d4
Reviewed-on: https://chromium-review.googlesource.com/740344
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#513288}
[modify] https://crrev.com/98b579c1f5a358508dc0cca855c687ed51ccd6f7/pdf/pdfium/fuzzers/pdfium_fuzzer_helper.cc

Project Member

Comment 8 by ClusterFuzz, Nov 2 2017

ClusterFuzz has detected this issue as fixed in range 513206:513315.

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Abrt
Crash Address: 0x7fff8e94bf06
Crash State:
  /usr/lib/libc++abi.dylib:x86_64
  /usr/lib/libc++abi.dylib:x86_64
  _objc_terminate
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=459180:459211
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=513206:513315

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 9 by ClusterFuzz, Nov 2 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Labels: -Test-Predator-AutoOwner Test-Predator-Auto-Owner

Sign in to add a comment