[llvm-bugs] Issue 50104 in oss-fuzz: llvm:clangd-fuzzer: Abrt in llvm::raw_ostream::copy_to_buffer

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Fri Aug 12 11:05:15 PDT 2022

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, igm... at gmail.com, sammccall at google.com, davg at google.com, mitchp at google.com, bigch... at gmail.com, eneyman at google.com, llvm-... at lists.llvm.org, jo... at devlieghere.com, jfb at chromium.org, v... at apple.com, mitch... at outlook.com, xpl... at gmail.com, akils... at apple.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Unreproducible OS-Linux Proj-llvm Engine-honggfuzz Reported-2022-08-12
Type: Bug

New issue 50104 by ClusterFuzz-External: llvm:clangd-fuzzer: Abrt in llvm::raw_ostream::copy_to_buffer

Detailed Report: https://oss-fuzz.com/testcase?key=5416609551876096

Project: llvm
Fuzzing Engine: honggfuzz
Fuzz Target: clangd-fuzzer
Job Type: honggfuzz_asan_llvm
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000108ae
Crash State:
Sanitizer: address (ASAN)

Crash Revision: https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&revision=202206280601

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5416609551876096

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.

************************* UNREPRODUCIBLE *************************
Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days, we've been seeing this crash frequently.

It may be possible to reproduce by trying the following options:
- Run testcase multiple times for a longer duration.
- Run fuzzing without testcase argument to hit the same crash signature.

If it still does not reproduce, try a speculative fix based on the crash stacktrace and verify if it works by looking at the crash statistics in the report. We will auto-close the bug if the crash is not seen for 14 days.
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:

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20220812/c9432366/attachment.html>

More information about the llvm-bugs mailing list