[llvm-bugs] Issue 15550 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_unswitch: ASSERT: NameRef.find_first_of(0) == StringRef::npos && "Null bytes are not allowed in na

[ClusterFuzz-External via monorail via llvm-bugs]

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 Reproducible Stability-Memory-MemorySanitizer  
Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-06-29
Type: Bug

New issue 15550 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_unswitch: ASSERT:  
NameRef.find_first_of(0) == StringRef::npos && "Null bytes are not allowed  
in na
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15550

Detailed report: https://oss-fuzz.com/testcase?key=5678507247534080

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_unswitch
Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_unswitch
Job Type: libfuzzer_msan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
   NameRef.find_first_of(0) == StringRef::npos && "Null bytes are not  
allowed in na
   llvm::Value::setNameImpl
   llvm::Value::setName

Sanitizer: memory (MSAN)

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

Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.

-- 
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190629/eab71ff8/attachment.html>