Ill in v8::Isolate::Initialize |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6072892320907264 Fuzzer: libFuzzer_v8_fully_instrumented_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Ill Crash Address: 0x00010187da5a Crash State: v8::Isolate::Initialize v8::Isolate::New Environment::Environment Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=552758:552888 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6072892320907264 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 26 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/5c9b30ae38101d89ea4d643b9b1dc087f184976e ([api] Split isolate allocation and initialization). 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.
,
Jul 24
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/096b80037b1a139265406e21057bc77a213ce607 commit 096b80037b1a139265406e21057bc77a213ce607 Author: Andreas Haas <ahaas@chromium.org> Date: Tue Jul 24 14:42:07 2018 [fuzzer] Add attributes to LLVMFuzzerInitialize definition That prevents the linker from dead-stripping the function, as it is not called directly, it is resolved in the runtime via dlsym(). I copied the change from https://crrev.com/c/833995 R=mmoroz@chromium.org Bug: 837098 Change-Id: I998517ebab623e67d275fe656643a8ee5fd1e951 Reviewed-on: https://chromium-review.googlesource.com/1148391 Reviewed-by: Max Moroz <mmoroz@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#577532} [modify] https://crrev.com/096b80037b1a139265406e21057bc77a213ce607/testing/libfuzzer/fuzzers/v8_fuzzer.cc
,
Jul 25
ClusterFuzz has detected this issue as fixed in range 577529:577581. Detailed report: https://clusterfuzz.com/testcase?key=6072892320907264 Fuzzer: libFuzzer_v8_fully_instrumented_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Ill Crash Address: 0x00010187da5a Crash State: v8::Isolate::Initialize v8::Isolate::New Environment::Environment Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=552758:552888 Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=577529:577581 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6072892320907264 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.
,
Jul 25
ClusterFuzz testcase 6072892320907264 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Apr 26 2018Labels: Test-Predator-Auto-Components