[llvm-bugs] Issue 7037 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in Db::parseEncoding
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Mar 20 13:09:48 PDT 2018
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 Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2018-03-20
Type: Bug
New issue 7037 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer:
Stack-overflow in Db::parseEncoding
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7037
Detailed report: https://oss-fuzz.com/testcase?key=5661424173973504
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-demangle-fuzzer
Fuzz target binary: llvm-demangle-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Stack-overflow
Crash Address: 0x7ffcfebbaf00
Crash State:
Db::parseEncoding
Db::parseName
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803190520:201803200524
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5661424173973504
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/20180320/06cc72af/attachment.html>
More information about the llvm-bugs
mailing list