[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-19 Thread monor… via monorail via llvm-bugs
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #10 on issue 3627 by monor...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c10 ClusterFuzz testcase 5935702182199296 is verified as fixed

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-19 Thread monor… via monorail via llvm-bugs
Comment #9 on issue 3627 by monor...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c9 ClusterFuzz has detected this issue as fixed in range 201710160455:201710190451. Detailed report: https://oss-fuzz.com/testcase

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-16 Thread k… via monorail via llvm-bugs
Comment #8 on issue 3627 by k...@google.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c8 We've raced :) Before r315933 this reproduced for me. Let OSS-Fuzz auto-close this bug. -- You received this message because: 1. You were specifically CC'd on the issue

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-16 Thread jus… via monorail via llvm-bugs
Comment #6 on issue 3627 by jus...@justinbogner.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c6 Sorry, by empty I mean that there's no IR. That is: % opt -S -o - clusterfuzz-testcase-minimized-5935702182199296.dms ; ModuleID = 'clusterfuzz-testcase-minimi

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-16 Thread k… via monorail via llvm-bugs
Comment #7 on issue 3627 by k...@google.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c7 I've fixed the fuzz target in r315933. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at:

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-16 Thread k… via monorail via llvm-bugs
Comment #5 on issue 3627 by k...@google.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c5 And the assertion is in libFuzzer that indicates that the fuzz target did not return 0 -- You received this message because: 1. You were specifically CC'd on the issu

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-16 Thread k… via monorail via llvm-bugs
Updates: Cc: jus...@justinbogner.com Comment #4 on issue 3627 by k...@google.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c4 The reproducer testcase is empty Hmm. 12 bytes for me ls -l ~/Downloads/clusterfuzz-testcase-minimized-5935702182199296 -rw

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-16 Thread jus… via monorail via llvm-bugs
Comment #3 on issue 3627 by jus...@justinbogner.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c3 The reproducer testcase is empty, so I think this is a crash in the mutator, rather than a bug found by fuzzing. -- You received this message because: 1. You

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-15 Thread monor… via monorail via llvm-bugs
Updates: Labels: ClusterFuzz-Top-Crash Comment #2 on issue 3627 by monor...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627#c2 Testcase 5935702182199296 is a top crash on ClusterFuzz for linux platform. Please

[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0

2017-10-12 Thread monor… via monorail via llvm-bugs
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Stability-LibFuzzer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-10-13 New issue 3627 by monor..