[llvm-bugs] Issue 17834 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-earlycse: Unknown error with empty stacktrace

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Mon Sep 30 17:38:52 PDT 2019

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... at gmail.com, mitchp at google.com, bigchees... at gmail.com,  
eneyman at google.com, llvm-b... at lists.llvm.org, jfb at chromium.org,  
v... at apple.com, mitchphi... at outlook.com, xpl... at gmail.com,  
akils... at apple.com
Labels: ClusterFuzz Stability-Memory-MemorySanitizer Unreproducible  
Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-10-01
Type: Bug

New issue 17834 by ClusterFuzz-External:  
llvm:llvm-opt-fuzzer--x86_64-earlycse: Unknown error with empty stacktrace

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

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-opt-fuzzer--x86_64-earlycse
Job Type: libfuzzer_msan_llvm
Platform Id: linux

Crash Type:
Crash Address:
Crash State:

Sanitizer: memory (MSAN)

Crash Revision:  

Reproducer Testcase:  

Issue filed automatically.

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

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. If you  
are unable to reproduce this, please try a speculative fix based on the  
crash stacktrace in the report. The fix can be verified by looking at the  
crash statistics in the report, a day after the fix is deployed. 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/20190930/a458dacb/attachment.html>

More information about the llvm-bugs mailing list