[llvm-bugs] Issue 14404 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !MangledName.empty()
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Apr 23 06:12:17 PDT 2019
Comment #3 on issue 14404 by ClusterFuzz-External:
llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !MangledName.empty()
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14404#c3
ClusterFuzz has detected this issue as fixed in range
201904220257:201904230302.
Detailed report: https://oss-fuzz.com/testcase?key=5643372422758400
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer
Fuzz target binary: llvm-microsoft-demangle-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: ASSERT
Crash Address:
Crash State:
!MangledName.empty()
llvm::ms_demangle::Demangler::demangleCharLiteral
llvm::ms_demangle::Demangler::demangleStringLiteral
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904220257:201904230302
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5643372422758400
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
instructions to reproduce this bug locally.
If you suspect that the result above is incorrect, try re-doing that job on
the test case report page.
--
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/20190423/0e5997fd/attachment-0001.html>
More information about the llvm-bugs
mailing list