[llvm-bugs] Issue 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Status: WontFix Comment #7 on issue 5020 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c7 ClusterFuzz testcase 4656722267340800 is flaky and no longer crashes, so closing issue. 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 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Labels: -Reproducible Unreproducible Comment #6 on issue 5020 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c6 ClusterFuzz testcase 4656722267340800 appears to be flaky, updating reproducibility label. -- 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 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Cc: eney...@google.com Comment #5 on issue 5020 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c5 (No comment was entered for this change.) -- 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 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Cc: j...@chromium.org Comment #4 on issue 5020 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c4 (No comment was entered for this change.) -- 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 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Labels: Deadline-Approaching Comment #3 on issue 5020 by sheriff...@chromium.org: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Cc: xpl...@gmail.com Comment #2 on issue 5020 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c2 (No comment was entered for this change.) -- 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 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-08 Type: Bug New issue 5020 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020 Detailed report: https://oss-fuzz.com/testcase?key=4656722267340800 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: width && "Can't truncate to 0 bits" llvm::APInt::trunc AnalyzeBitFieldAssignment Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201712090607:201712100011 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4656722267340800 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
