[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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?key=5935702182199296 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Res == 0 _start Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710121744:201710130152 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710160455:201710190451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5935702182199296 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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 You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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-minimized-5935702182199296.dms' source_filename = "clusterfuzz-testcase-minimized-5935702182199296.dms" I think 12 bytes is approximately the smallest valid bitcode file. In any case, this doesn't seem to reproduce with current ToT, and I see that it happened while we were changing how llvm's OSS Fuzz flags worked. I suspect this was a transient issue. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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 issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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-r- 1 kcc eng 12 Oct 16 13:20 -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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 prioritize fixing this crash. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3627 in oss-fuzz: ASSERT: Res == 0
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...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Res == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3627 Detailed report: https://oss-fuzz.com/testcase?key=5935702182199296 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Res == 0 _start Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710121744:201710130152 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5935702182199296 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
