Integer-overflow in ppparse |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5675371428315136 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: ppparse pp::ExpressionParser::parse pp::DirectiveParser::parseExpressionIf Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=521492:521536 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5675371428315136 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 26 2017
Since it is related to Swiftshader component, assigning it to capn@ capn@ could you please look into it Thank You...
,
Jan 2 2018
The undefined behavior is also undefined behavior in the shading language that this code compiles, so this is totally benign.
,
Dec 1
ClusterFuzz testcase 5675371428315136 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
, Dec 22 2017Labels: Test-Predator-Auto-Components