[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #21 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c21 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-52f61563-ce5d-4211-967e-de76bec0bd75.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 71315 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::APInt::udiv
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 71315 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::APInt::udiv https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71315#c1 ClusterFuzz testcase 4615016394915840 is verified as fixed in https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&range=202408180613:202408190620 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #20 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c20 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-bd167456-6960-4e17-9bf1-1e6bab0aaf60.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 71315 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::APInt::udiv
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible OS-Linux Proj-llvm Engine-honggfuzz Reported-2024-08-20 Type: Bug New issue 71315 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::APInt::udiv https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71315 Detailed Report: https://oss-fuzz.com/testcase?key=4615016394915840 Project: llvm Fuzzing Engine: honggfuzz Fuzz Target: clang-fuzzer Job Type: honggfuzz_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x053900022e6d Crash State: llvm::APInt::udiv llvm::APSInt::operator/ ComplexExprEvaluator::VisitBinaryOperator Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&revision=202206140606 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4615016394915840 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 36067 in oss-fuzz: llvm:clang-objc-fuzzer: Abrt in llvm::APInt::udiv
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 36067 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Abrt in llvm::APInt::udiv https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36067#c4 ClusterFuzz testcase 4785734782418944 is verified as fixed in https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&range=202408180613:202408190620 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #19 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c19 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-c3168514-e8f4-41bc-a6d7-ff311cc73921.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #18 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c18 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-4a6483d4-f63e-4048-a622-08140bf6dfcf.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #17 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c17 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-2daeb518-d110-414b-8552-19afd1e312fb.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #16 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c16 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-597be428-a56f-4cde-a472-ed3598348d5d.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #15 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c15 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-ccc82e4a-c792-44bc-850e-f043c58217f5.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #14 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c14 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-17fa47ac-bb74-4d5d-b3a1-ee27ea65c6e5.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #13 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c13 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-e31b7614-bb86-4256-aaa0-aa9db8cf57e8.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #12 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c12 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-7c7849ac-76ff-40d9-93b1-e451cb0ea19b.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #11 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c11 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-27698c0d-1213-483d-9835-944ecd192c8e.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64774 in oss-fuzz: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: EltSize * 8 == EltVT.getFixedSizeInBits() && "Converting bits to bytes lost prec
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 64774 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: EltSize * 8 == EltVT.getFixedSizeInBits() && "Converting bits to bytes lost prec https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64774#c1 ClusterFuzz testcase 6350802658394112 is verified as fixed in https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&range=202406130628:202406140627 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #10 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c10 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-6b85aa81-a3b6-4e96-9457-2468253f6141.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #9 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c9 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-df507395-faf9-4b22-848d-591c53d9f2d0.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #8 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c8 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-6e0d2092-208a-45cd-a6a8-054662cc2a88.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #7 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c7 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-2b472f7f-79ff-4b9a-b248-139225040e44.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 69235 in oss-fuzz: llvm:clang-pseudo-fuzzer: Stack-overflow in auto clang::pseudo::glrRecover
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible OS-Linux Proj-llvm Engine-honggfuzz Reported-2024-05-25 Type: Bug New issue 69235 by ClusterFuzz-External: llvm:clang-pseudo-fuzzer: Stack-overflow in auto clang::pseudo::glrRecover https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=69235 Detailed Report: https://oss-fuzz.com/testcase?key=5086212514709504 Project: llvm Fuzzing Engine: honggfuzz Fuzz Target: clang-pseudo-fuzzer Job Type: honggfuzz_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7f7fef38 Crash State: auto clang::pseudo::glrRecover Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&range=202404290618:202404300633 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5086212514709504 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #6 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c6 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-b229cd25-dc3d-4a74-bcde-e671697c6801.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 50183 in oss-fuzz: llvm:clang-pseudo-fuzzer: Stack-overflow in auto clang::pseudo::glrRecover
Updates: Status: WontFix Comment #2 on issue 50183 by ClusterFuzz-External: llvm:clang-pseudo-fuzzer: Stack-overflow in auto clang::pseudo::glrRecover https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50183#c2 ClusterFuzz testcase 5110472596127744 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #5 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c5 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-edf278bb-b286-4271-a5f8-d6a81890b4bb.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 61478 in oss-fuzz: llvm:clang-objc-fuzzer: Abrt in clang::Sema::PushDeclContext
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 61478 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Abrt in clang::Sema::PushDeclContext https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=61478#c2 ClusterFuzz testcase 4910872609554432 is verified as fixed in https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&range=202405130622:202405140615 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65090 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-strength_reduce: Abrt in llvm-opt-fuzzer.cpp
Updates: Status: WontFix Comment #1 on issue 65090 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-strength_reduce: Abrt in llvm-opt-fuzzer.cpp https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65090#c1 ClusterFuzz testcase 5481500648538112 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65424 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Stack-overflow in p_ere
Updates: Status: WontFix Comment #1 on issue 65424 by ClusterFuzz-External: llvm:llvm-special-case-list-fuzzer: Stack-overflow in p_ere https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65424#c1 ClusterFuzz testcase 5593834478174208 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #4 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c4 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-fa9511e1-c91e-466a-95b4-4cf17cabe584.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64879 in oss-fuzz: llvm:llvm-dlang-demangle-fuzzer: Stack-overflow in Demangler::parseType
Updates: Status: WontFix Comment #1 on issue 64879 by ClusterFuzz-External: llvm:llvm-dlang-demangle-fuzzer: Stack-overflow in Demangler::parseType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64879#c1 ClusterFuzz testcase 6687178675322880 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #3 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c3 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-3bca22fd-bf78-418f-969b-414aae6d9f3d.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68574 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::RecursiveASTVisitor::TraverseCXXRecordDecl
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-05-02 Type: Bug New issue 68574 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::RecursiveASTVisitor::TraverseCXXRecordDecl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68574 Detailed Report: https://oss-fuzz.com/testcase?key=5493803875696640 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd9f70afd8 Crash State: clang::RecursiveASTVisitor::TraverseCXXRecordDecl clang::RecursiveASTVisitor::TraverseDecl Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202203030601:202203040606 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5493803875696640 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68540 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::DWARFUnitIndex::parseImpl
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2024-05-02 Type: Bug-Security New issue 68540 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::DWARFUnitIndex::parseImpl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68540 Detailed Report: https://oss-fuzz.com/testcase?key=5965613558005760 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Heap-buffer-overflow WRITE 8 Crash Address: 0x60300950 Crash State: llvm::DWARFUnitIndex::parseImpl llvm::DWARFUnitIndex::parse ThreadUnsafeDWARFContextState::getCUIndex Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011020601:202011030620 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5965613558005760 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68532 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !E->isValueDependent()
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible OS-Linux Proj-llvm Engine-honggfuzz Reported-2024-05-02 Type: Bug New issue 68532 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !E->isValueDependent() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68532 Detailed Report: https://oss-fuzz.com/testcase?key=4779661669040128 Project: llvm Fuzzing Engine: honggfuzz Fuzz Target: clang-fuzzer Job Type: honggfuzz_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !E->isValueDependent() EvaluateInPlace RecordExprEvaluator::VisitLambdaExpr Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&range=202209070608:202209080609 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4779661669040128 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68530 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !Info.Ctx.getLangOpts().CPlusPlus11 && "missing temporary materialization conver
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-05-02 Type: Bug New issue 68530 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !Info.Ctx.getLangOpts().CPlusPlus11 && "missing temporary materialization conver https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68530 Detailed Report: https://oss-fuzz.com/testcase?key=4706278256017408 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !Info.Ctx.getLangOpts().CPlusPlus11 && "missing temporary materialization conver ExprEvaluatorBase::VisitMemberExpr ExprEvaluatorBase::VisitStmtExpr Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202108040600:202201250612 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4706278256017408 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68529 in oss-fuzz: llvm:clang-format-fuzzer: Stack-overflow in unsigned int clang::format::AlignTokens
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-05-02 Type: Bug New issue 68529 by ClusterFuzz-External: llvm:clang-format-fuzzer: Stack-overflow in unsigned int clang::format::AlignTokenshttps://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68529 Detailed Report: https://oss-fuzz.com/testcase?key=4681308711223296 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-format-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd2df89fa8 Crash State: unsigned int clang::format::AlignTokenshttps://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202101250607:202101260626 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4681308711223296 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68528 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible OS-Linux Proj-llvm Engine-honggfuzz Reported-2024-05-02 Type: Bug New issue 68528 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68528 Detailed Report: https://oss-fuzz.com/testcase?key=4539025012424704 Project: llvm Fuzzing Engine: honggfuzz Fuzz Target: llvm-opt-fuzzer--x86_64-earlycse Job Type: honggfuzz_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v llvm::Value::Value llvm::Argument::Argument Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&revision=202312110610 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4539025012424704 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64784 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: (It == ParentBB->end() || It->getParent() == ParentBB) && "It not in ParentBB"
Updates: Status: WontFix Comment #1 on issue 64784 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: (It == ParentBB->end() || It->getParent() == ParentBB) && "It not in ParentBB" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64784#c1 ClusterFuzz testcase 5190036190265344 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #2 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c2 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-8dcc0a7b-9ee8-4a22-8541-df5af281608d.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68415 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in llvm::DataExtractor::getU8
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-30 Type: Bug New issue 68415 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in llvm::DataExtractor::getU8 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68415 Detailed Report: https://oss-fuzz.com/testcase?key=6257425133993984 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: llvm::DataExtractor::getU8 llvm::DWARFExpression::Operation::extract llvm::DWARFExpression::print Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202004090442:202004100305 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6257425133993984 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68401 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-30 Type: Bug New issue 68401 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68401 Detailed Report: https://oss-fuzz.com/testcase?key=5749124381278208 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal llvm::DWARFFormValue::extractValue llvm::DWARFDebugNames::NameIndex::getEntry Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801290646:201801300702 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5749124381278208 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68400 in oss-fuzz: llvm:clang-fuzzer: ASSERT: DD && "queried property of class with no definition"
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-30 Type: Bug New issue 68400 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: DD && "queried property of class with no definition" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68400 Detailed Report: https://oss-fuzz.com/testcase?key=5747178676420608 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: DD && "queried property of class with no definition" clang::CXXRecordDecl::data clang::Sema::FinalizeVarWithDestructor Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=201909210337 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5747178676420608 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68383 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-30 Type: Bug New issue 68383 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68383 Detailed Report: https://oss-fuzz.com/testcase?key=4525671903002624 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x05393921 Crash State: llvm::llvm_unreachable_internal CXXNameMangler::mangleExpression CXXNameMangler::mangleExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202006110252:202006121812 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4525671903002624 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65216 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: Idx >= 0 && "Invalid basic block argument!"
Updates: Status: WontFix Comment #1 on issue 65216 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: Idx >= 0 && "Invalid basic block argument!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65216#c1 ClusterFuzz testcase 6677353610477568 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 43221 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer"
Updates: Status: WontFix Comment #4 on issue 43221 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43221#c4 ClusterFuzz testcase 6631396272111616 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 51196 in oss-fuzz: llvm:clang-fuzzer: ASSERT: B > 0 && "Bit width can't be 0."
Updates: Status: WontFix Comment #2 on issue 51196 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: B > 0 && "Bit width can't be 0." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51196#c2 ClusterFuzz testcase 6605178781958144 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 51229 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::RecursiveASTVisitor::TraverseDecl
Updates: Status: WontFix Comment #2 on issue 51229 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::RecursiveASTVisitor::TraverseDecl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51229#c2 ClusterFuzz testcase 6594598375391232 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65374 in oss-fuzz: llvm:llvm-yaml-parser-fuzzer: Stack-overflow in void llvm::yaml::skip
Updates: Status: WontFix Comment #1 on issue 65374 by ClusterFuzz-External: llvm:llvm-yaml-parser-fuzzer: Stack-overflow in void llvm::yaml::skip https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65374#c1 ClusterFuzz testcase 6540028272508928 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 33042 in oss-fuzz: llvm:llvm-microsoft-demangle-fuzzer: Stack-overflow in llvm::ms_demangle::Demangler::parse
Updates: Status: WontFix Comment #4 on issue 33042 by ClusterFuzz-External: llvm:llvm-microsoft-demangle-fuzzer: Stack-overflow in llvm::ms_demangle::Demangler::parse https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33042#c4 ClusterFuzz testcase 6527584180502528 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64776 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: Null-dereference READ in llvm::StructType::getTypeAtIndex
Updates: Status: WontFix Comment #1 on issue 64776 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: Null-dereference READ in llvm::StructType::getTypeAtIndex https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64776#c1 ClusterFuzz testcase 6517670174130176 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 33328 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::Parser::SkipUntil
Updates: Status: WontFix Comment #4 on issue 33328 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::Parser::SkipUntil https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33328#c4 ClusterFuzz testcase 6441486293008384 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64924 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal
Updates: Status: WontFix Comment #1 on issue 64924 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64924#c1 ClusterFuzz testcase 6432838563790848 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 50278 in oss-fuzz: llvm:clang-fuzzer: Use-of-uninitialized-value in clang::TemplateName::getKind
Updates: Status: WontFix Comment #2 on issue 50278 by ClusterFuzz-External: llvm:clang-fuzzer: Use-of-uninitialized-value in clang::TemplateName::getKind https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50278#c2 ClusterFuzz testcase 6249243525906432 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65483 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: Unexpected-exit in llvm::LLVMContext::diagnose
Updates: Status: WontFix Comment #1 on issue 65483 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: Unexpected-exit in llvm::LLVMContext::diagnose https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65483#c1 ClusterFuzz testcase 6150347533910016 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 52015 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseDirectDeclarator
Updates: Status: WontFix Comment #2 on issue 52015 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseDirectDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=52015#c2 ClusterFuzz testcase 6031855258566656 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 20946 in oss-fuzz: llvm:clang-fuzzer: Null-dereference READ in GetFullTypeForDeclarator
Updates: Status: WontFix Comment #7 on issue 20946 by ClusterFuzz-External: llvm:clang-fuzzer: Null-dereference READ in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20946#c7 ClusterFuzz testcase 5970362481508352 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 53447 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::TypePropertyCache::ensure
Updates: Status: WontFix Comment #2 on issue 53447 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::TypePropertyCache::ensure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53447#c2 ClusterFuzz testcase 5903883046354944 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 26936 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !isValueDependent() && "Expression evaluator can't be called on a dependent expr
Updates: Status: WontFix Comment #5 on issue 26936 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !isValueDependent() && "Expression evaluator can't be called on a dependent expr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26936#c5 ClusterFuzz testcase 5757580271681536 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15924 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E
Updates: Status: WontFix Comment #6 on issue 15924 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15924#c6 ClusterFuzz testcase 5750352378331136 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 20938 in oss-fuzz: llvm:clang-fuzzer: Null-dereference READ in processTypeAttrs
Updates: Status: WontFix Comment #7 on issue 20938 by ClusterFuzz-External: llvm:clang-fuzzer: Null-dereference READ in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20938#c7 ClusterFuzz testcase 5705616855400448 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 49199 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Status: WontFix Comment #3 on issue 49199 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49199#c3 ClusterFuzz testcase 5566192374382592 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64824 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v
Updates: Status: WontFix Comment #1 on issue 64824 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64824#c1 ClusterFuzz testcase 5345559573299200 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 39058 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer"
Updates: Status: WontFix Comment #4 on issue 39058 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=39058#c4 ClusterFuzz testcase 5328159822708736 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 30308 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Crash in llvm::DWARFUnitIndex::parseImpl
Updates: Status: WontFix Comment #5 on issue 30308 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Crash in llvm::DWARFUnitIndex::parseImpl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30308#c5 ClusterFuzz testcase 5289587515719680 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65067 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: (getOperand(0)->getType()->isIntOrIntVectorTy() || getOperand(0)->getType()->isP
Updates: Status: WontFix Comment #1 on issue 65067 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: (getOperand(0)->getType()->isIntOrIntVectorTy() || getOperand(0)->getType()->isP https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65067#c1 ClusterFuzz testcase 5282853872861184 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64706 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Status: WontFix Comment #1 on issue 64706 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64706#c1 ClusterFuzz testcase 5207109557026816 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 26130 in oss-fuzz: llvm:clang-fuzzer: ASSERT: SS == getCurFunction()->SwitchStack.back().getPointer() && "switch stack missing
Updates: Status: WontFix Comment #5 on issue 26130 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: SS == getCurFunction()->SwitchStack.back().getPointer() && "switch stack missing https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26130#c5 ClusterFuzz testcase 5188216376000512 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 51257 in oss-fuzz: llvm:clang-fuzzer: ASSERT: DD && "queried property of class with no definition"
Updates: Status: WontFix Comment #2 on issue 51257 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: DD && "queried property of class with no definition" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51257#c2 ClusterFuzz testcase 5176200262713344 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 27444 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in unsigned char llvm::DataExtractor::getU
Updates: Status: WontFix Comment #5 on issue 27444 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in unsigned char llvm::DataExtractor::getU https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27444#c5 ClusterFuzz testcase 5162010651918336 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 25883 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: D && !D->isInvalidDecl() && D->isThisDeclarationADefinition() && "Invalid interf
Updates: Status: WontFix Comment #5 on issue 25883 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: D && !D->isInvalidDecl() && D->isThisDeclarationADefinition() && "Invalid interf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25883#c5 ClusterFuzz testcase 5155506841452544 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64819 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !(Rewrite.second).empty() && "Expected to find Predicates"
Updates: Status: WontFix Comment #1 on issue 64819 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !(Rewrite.second).empty() && "Expected to find Predicates" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64819#c1 ClusterFuzz testcase 5152493814022144 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64844 in oss-fuzz: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: MBB != &MF->front() && "Can't find reaching def for virtreg"
Updates: Status: WontFix Comment #1 on issue 64844 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: MBB != &MF->front() && "Can't find reaching def for virtreg" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64844#c1 ClusterFuzz testcase 5150786497413120 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 29182 in oss-fuzz: llvm:clang-fuzzer: ASSERT: RT->getDecl()->isUnion() && "RecordType is expected to be a union."
Updates: Status: WontFix Comment #5 on issue 29182 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: RT->getDecl()->isUnion() && "RecordType is expected to be a union." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=29182#c5 ClusterFuzz testcase 5108635363573760 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 25116 in oss-fuzz: llvm:clang-fuzzer: Use-of-uninitialized-value in clang::Parser::ParseCastExpression
Updates: Status: WontFix Comment #5 on issue 25116 by ClusterFuzz-External: llvm:clang-fuzzer: Use-of-uninitialized-value in clang::Parser::ParseCastExpression https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25116#c5 ClusterFuzz testcase 5079246079524864 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 61171 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !E->isValueDependent()
Updates: Status: WontFix Comment #2 on issue 61171 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !E->isValueDependent() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=61171#c2 ClusterFuzz testcase 5063461829476352 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 47859 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Status: WontFix Comment #3 on issue 47859 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47859#c3 ClusterFuzz testcase 5017701967331328 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 52803 in oss-fuzz: llvm:clangd-fuzzer: ASSERT: false && "Invalid UTF-8 in value used as JSON"
Updates: Status: WontFix Comment #2 on issue 52803 by ClusterFuzz-External: llvm:clangd-fuzzer: ASSERT: false && "Invalid UTF-8 in value used as JSON" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=52803#c2 ClusterFuzz testcase 4968997926076416 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 33628 in oss-fuzz: llvm:clang-fuzzer: ASSERT: D.isPastIdentifier() && "Haven't past the location of the identifier yet?"
Updates: Status: WontFix Comment #4 on issue 33628 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: D.isPastIdentifier() && "Haven't past the location of the identifier yet?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33628#c4 ClusterFuzz testcase 4915113116172288 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65071 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Use-of-uninitialized-value in llvm::StringMapImpl::LookupBucketFor
Updates: Status: WontFix Comment #1 on issue 65071 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Use-of-uninitialized-value in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65071#c1 ClusterFuzz testcase 4868581756370944 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 42816 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: isExpansion() && "Not a macro expansion SLocEntry!"
Updates: Status: WontFix Comment #4 on issue 42816 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: isExpansion() && "Not a macro expansion SLocEntry!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=42816#c4 ClusterFuzz testcase 4867253789655040 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 20708 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Abrt in llvm::report_fatal_error
Updates: Status: WontFix Comment #6 on issue 20708 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Abrt in llvm::report_fatal_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20708#c6 ClusterFuzz testcase 4842207976882176 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65323 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: detail::isPresent(Val) && "dyn_cast on a non-existent value"
Updates: Status: WontFix Comment #1 on issue 65323 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-strength_reduce: ASSERT: detail::isPresent(Val) && "dyn_cast on a non-existent value" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65323#c1 ClusterFuzz testcase 4809525047656448 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64799 in oss-fuzz: llvm:llvm-yaml-parser-fuzzer: Stack-overflow in llvm::yaml::SequenceNode::increment
Updates: Status: WontFix Comment #1 on issue 64799 by ClusterFuzz-External: llvm:llvm-yaml-parser-fuzzer: Stack-overflow in llvm::yaml::SequenceNode::increment https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64799#c1 ClusterFuzz testcase 4785852924166144 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 58176 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in DataRecursiveIntBinOpEvaluator::enqueue
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 58176 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in DataRecursiveIntBinOpEvaluator::enqueue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58176#c2 ClusterFuzz testcase 4783466800873472 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404280611:202404290618 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 30614 in oss-fuzz: llvm:clang-format-fuzzer: Stack-overflow in unsigned int clang::format::AlignTokens
Updates: Status: WontFix Comment #4 on issue 30614 by ClusterFuzz-External: llvm:clang-format-fuzzer: Stack-overflow in unsigned int clang::format::AlignTokenshttps://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30614#c4 ClusterFuzz testcase 4740907859574784 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 56645 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !Info.Ctx.getLangOpts().CPlusPlus11 && "missing temporary materialization conver
Updates: Status: WontFix Comment #2 on issue 56645 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !Info.Ctx.getLangOpts().CPlusPlus11 && "missing temporary materialization conver https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56645#c2 ClusterFuzz testcase 4687194185400320 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 65168 in oss-fuzz: llvm:clang-format-fuzzer: ASSERT: PPBranchLevel < (int)PPLevelBranchIndex.size()
Updates: Status: WontFix Comment #1 on issue 65168 by ClusterFuzz-External: llvm:clang-format-fuzzer: ASSERT: PPBranchLevel < (int)PPLevelBranchIndex.size() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65168#c1 ClusterFuzz testcase 4565836287049728 is closed as invalid, so closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68379 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-30 Type: Bug New issue 68379 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68379 Detailed Report: https://oss-fuzz.com/testcase?key=6581677716471808 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x053939a5 Crash State: llvm::llvm_unreachable_internal clang::Sema::ActOnPseudoDestructorExpr clang::Parser::ParseCXXPseudoDestructor Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202401170617:202404160629 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6581677716471808 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 53695 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in visitLocalsRetainedByInitializer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 53695 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in visitLocalsRetainedByInitializer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53695#c2 ClusterFuzz testcase 6104989057810432 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404280611:202404290618 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 61972 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in llvm::SmallSet
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 61972 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in llvm::SmallSet https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=61972#c2 ClusterFuzz testcase 5370399557550080 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404280611:202404290618 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 64793 in oss-fuzz: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: !MI.isTerminator()
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 64793 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: !MI.isTerminator() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64793#c1 ClusterFuzz testcase 4606761646292992 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404270612:202404280611 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68296 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: (getLangOpts().CPlusPlus || isBoundsAttrContext()) && "building reference to fie
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-25 Type: Bug New issue 68296 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: (getLangOpts().CPlusPlus || isBoundsAttrContext()) && "building reference to fie https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68296 Detailed Report: https://oss-fuzz.com/testcase?key=6302419160989696 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: (getLangOpts().CPlusPlus || isBoundsAttrContext()) && "building reference to fie clang::Sema::BuildDeclarationNameExpr clang::Sema::BuildDeclarationNameExpr Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202401170617:202404160629 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6302419160989696 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 56866 in oss-fuzz: llvm:clang-format-fuzzer: Null-dereference READ in clang::format::FormatToken::closesScopeAfterBlock
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 56866 by ClusterFuzz-External: llvm:clang-format-fuzzer: Null-dereference READ in clang::format::FormatToken::closesScopeAfterBlock https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56866#c2 ClusterFuzz testcase 4545647270559744 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404230613:202404240626 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure
Comment #1 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c1 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-a3c71e8d-674e-4f2c-aeb7-b5aca4310fef.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68209 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 68209 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68209#c1 ClusterFuzz testcase 6549360285384704 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404210604:202404220616 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68274 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-gisel: ASSERT: idx < size()
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-25 Type: Bug New issue 68274 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-gisel: ASSERT: idx < size() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68274 Detailed Report: https://oss-fuzz.com/testcase?key=5136749601816576 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: idx < size() llvm::LegalizerHelper::fewerElementsVectorExtractInsertVectorElt llvm::LegalizerHelper::fewerElementsVector Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202312050608:202312060616 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5136749601816576 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68239 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: verifyVPlanIsValid(*Plan) && "VPlan is invalid"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 68239 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: verifyVPlanIsValid(*Plan) && "VPlan is invalid" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68239#c1 ClusterFuzz testcase 5788250825359360 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404160629:202404170622 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 46239 in oss-fuzz: llvm:clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 46239 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46239#c4 ClusterFuzz testcase 5307221933686784 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202404220616:202404230613 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68239 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: verifyVPlanIsValid(*Plan) && "VPlan is invalid"
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-22 Type: Bug New issue 68239 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: verifyVPlanIsValid(*Plan) && "VPlan is invalid" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68239 Detailed Report: https://oss-fuzz.com/testcase?key=5788250825359360 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-loop_vectorize Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: verifyVPlanIsValid(*Plan) && "VPlan is invalid" llvm::LoopVectorizationPlanner::buildVPlansWithVPRecipes llvm::LoopVectorizationPlanner::plan Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202401170617:202404160629 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5788250825359360 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68209 in oss-fuzz: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-21 Type: Bug New issue 68209 by ClusterFuzz-External: llvm:clang-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68209 Detailed Report: https://oss-fuzz.com/testcase?key=6549360285384704 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x05391c2e Crash State: llvm::llvm_unreachable_internal clang::StmtVisitorBase::Visit clang::Stmt::printPretty Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202401170617:202404160629 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6549360285384704 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68200 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-O2: ASSERT: Ret.getOpcode() == ISD::MERGE_VALUES && "Ret value is a collection of constituen
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-21 Type: Bug New issue 68200 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-O2: ASSERT: Ret.getOpcode() == ISD::MERGE_VALUES && "Ret value is a collection of constituen https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68200 Detailed Report: https://oss-fuzz.com/testcase?key=4888123877163008 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Ret.getOpcode() == ISD::MERGE_VALUES && "Ret value is a collection of constituen llvm::TargetLowering::forceExpandWideMUL llvm::TargetLowering::forceExpandWideMUL Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202401170617:202404160629 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4888123877163008 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 68187 in oss-fuzz: llvm:llvm-parse-assembly-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2024-04-20 Type: Bug New issue 68187 by ClusterFuzz-External: llvm:llvm-parse-assembly-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68187 Detailed Report: https://oss-fuzz.com/testcase?key=5384316113715200 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-parse-assembly-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E llvm::LLParser::PerFunctionState::getVal llvm::LLParser::convertValIDToValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202401170617:202404160629 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5384316113715200 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
