[llvm-bugs] Issue 3216 in oss-fuzz: llvm: ASSERT: result <= UINT32_MAX

2017-10-24 Thread monor… via monorail via llvm-bugs
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #8 on issue 3216 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: result <= UINT32_MAX https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3216#c8 ClusterFuzz testcase 4513701640011776 is

[llvm-bugs] Issue 3216 in oss-fuzz: llvm: ASSERT: result <= UINT32_MAX

2017-10-24 Thread monor… via monorail via llvm-bugs
Comment #7 on issue 3216 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: result <= UINT32_MAX https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3216#c7 ClusterFuzz has detected this issue as fixed in range 201710230449:201710240446. Detailed report: https://o

[llvm-bugs] Issue 3216 in oss-fuzz: llvm: ASSERT: result <= UINT32_MAX

2017-10-10 Thread monor… via monorail via llvm-bugs
Updates: Cc: v...@apple.com Comment #6 on issue 3216 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: result <= UINT32_MAX https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3216#c6 (No comment was entered for this change.) -- You received this message bec

[llvm-bugs] Issue 3216 in oss-fuzz: llvm: ASSERT: result <= UINT32_MAX

2017-09-08 Thread monor… via monorail via llvm-bugs
Updates: Labels: ClusterFuzz-Top-Crash Comment #5 on issue 3216 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: result <= UINT32_MAX https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3216#c5 Testcase 4513701640011776 is a top crash on ClusterFuzz for linu