Sanitizer CHECK failure in ((data_.proc_self_maps.len)) > ((0)) (0, 0) |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5708084801699840 Fuzzer: inferno_twister Job Type: linux_ubsan_vptr_chrome Platform Id: linux Crash Type: Sanitizer CHECK failure Crash Address: Crash State: ((data_.proc_self_maps.len)) > ((0)) (0, 0) Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=463867:463893 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5708084801699840 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 19 2017
Peter, I believe that you've fixed that recently, but we are still waiting for the next clang roll: issue 787920 .
,
Jan 5 2018
Roll has been in for two days, this should be fixed.
,
Jan 12 2018
ClusterFuzz testcase 5708084801699840 is still reproducing on tip-of-tree build (trunk). Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, Dec 19 2017Components: Internals>Media
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage