[llvm-bugs] Issue 8699 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Out-of-memory in llvm_llvm-dwarfdump-fuzzer

[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, llvm-b... at lists.llvm.org, v... at apple.com,  
mitchphi... at outlook.com, xpl... at gmail.com, akils... at apple.com
Labels: ClusterFuzz Reproducible Engine-libfuzzer Proj-llvm  
Reported-2018-06-02
Type: Bug

New issue 8699 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer:  
Out-of-memory in llvm_llvm-dwarfdump-fuzzer
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8699

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

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

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address:
Crash State:
   llvm_llvm-dwarfdump-fuzzer

Sanitizer: address (ASAN)

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

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

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 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.

-- 
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/20180602/56d06b16/attachment.html>