[llvm-bugs] Issue 4390 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Sanitizer CHECK failure in "((0)) != (0)" (0x0, 0x0)

[monor… via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
llvm-b... at lists.llvm.org, v... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-11-23
Type: Bug

New issue 4390 by monor... at clusterfuzz-external.iam.gserviceaccount.com:  
llvm/llvm-dwarfdump-fuzzer: Sanitizer CHECK failure in "((0)) != (0)" (0x0,  
0x0)
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4390

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

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer
Fuzz target binary: llvm-dwarfdump-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address:
Crash State:
   "((0)) != (0)" (0x0, 0x0)

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201708280446:201708291805

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

Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.

When you fix this bug, please
   * mention the fix revision(s).
   * state whether the bug was a short-lived regression or an old bug in any  
stable releases.
   * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.

-- 
You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

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