[llvm-bugs] Issue 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #4 on issue 12897 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897#c4 https://reviews.llvm.org/D60202 fixes at

[llvm-bugs] Issue 12432 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #5 on issue 12432 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12432#c5 Fix: https://reviews.llvm.org/D60206 -- You received this message because: 1. You were specifically CC'd

[llvm-bugs] Issue 13260 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #3 on issue 13260 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13260#c3 Fix for all of these: https://reviews.llvm.org/D60207 -- You received this message

[llvm-bugs] Issue 12438 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #5 on issue 12438 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12438#c5 Fix: https://reviews.llvm.org/D60202 -- You received this message because: 1. You were

[llvm-bugs] Issue 12435 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #5 on issue 12435 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12435#c5 Fix: https://reviews.llvm.org/D60202 -- You received this

[llvm-bugs] Issue 12429 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #5 on issue 12429 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12429#c5 Fix: https://reviews.llvm.org/D60204 -- You received

[llvm-bugs] Issue 13260 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #2 on issue 13260 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13260#c2 The original test case is '? @@ YMMC@' The slightly shorter one '? @@ YC@'

[llvm-bugs] Issue 12428 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()

2019-04-03 Thread thavia monorail via llvm-bugs
Comment #5 on issue 12428 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12428#c5 Fix: https://reviews.llvm.org/D60204 -- You received this message because: 1. You were specifically CC'd on the issue You

[llvm-bugs] Issue 12428 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()

2019-04-05 Thread thavia monorail via llvm-bugs
Comment #7 on issue 12428 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12428#c7 Hooray, the fix (https://reviews.llvm.org/rL357647) worked. Can someone close this? -- You received this message because:

[llvm-bugs] Issue 14084 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output

2019-04-07 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14084 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14084#c2 Fix: https://reviews.llvm.org/D60354 -- You received

[llvm-bugs] Issue 14123 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference WRITE in llvm::ms_demangle::Demangler::demangleMemberPointerType

2019-04-07 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14123 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference WRITE in llvm::ms_demangle::Demangler::demangleMemberPointerType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14123#c2 Fix: https://reviews.llvm.org/D60354 -- You received this

[llvm-bugs] Issue 14122 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle

2019-04-07 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14122 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14122#c2 Fix: https://reviews.llvm.org/D60354 -- You received this message because: 1. You were

[llvm-bugs] Issue 14121 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()

2019-04-07 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14121 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14121#c2 Fix: https://reviews.llvm.org/D60354 -- You received this message because: 1. You were specifically CC'd on the issue You

[llvm-bugs] Issue 14222 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !MangledName.empty()

2019-04-14 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14222 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !MangledName.empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14222#c2 https://reviews.llvm.org/rL358363 should fix this. -- You received this message because: 1. You were

[llvm-bugs] Issue 14239 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()

2019-04-14 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14239 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14239#c2 http://reviews.llvm.org/rL358367 should fix. -- You received this message because: 1. You were specifically CC'd on the

[llvm-bugs] Issue 12429 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode

2019-04-12 Thread thavia monorail via llvm-bugs
Comment #7 on issue 12429 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12429#c7 I hadn't realized CF's test case had a trailing

[llvm-bugs] Issue 14201 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Stack-overflow in llvm::ms_demangle::Demangler::demangleTemplateInstantiationName

2019-04-12 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14201 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Stack-overflow in llvm::ms_demangle::Demangler::demangleTemplateInstantiationName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14201#c2 Hopefully fixed by http://reviews.llvm.org/rL358234 --

[llvm-bugs] Issue 14206 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()

2019-04-12 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14206 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14206#c2 Should be fixed in http://reviews.llvm.org/rL358238 (which I found a bit before CF). -- You received this message

[llvm-bugs] Issue 14247 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray

2019-04-16 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14247 by tha...@google.com: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14247#c2 https://reviews.llvm.org/D60774 should fix

[llvm-bugs] Issue 14278 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::StructorIdentifierNode::output

2019-04-16 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14278 by tha...@google.com: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::StructorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14278#c2 http://reviews.llvm.org/rL358491 should fix. -- You received this

[llvm-bugs] Issue 14221 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer

2019-05-26 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14221 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14221#c2 r361744 should fix this. -- You received this message because: 1. You were

[llvm-bugs] Issue 15022 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer

2019-06-05 Thread thavia monorail via llvm-bugs
Comment #2 on issue 15022 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15022#c2 The root cause here ultimately is that demangling output can be exponential in the

[llvm-bugs] Issue 14405 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleTemplateParameterList

2019-05-22 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14405 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleTemplateParameterList https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14405#c2 361402 should fix this. -- You received this message

[llvm-bugs] Issue 14349 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Direct-leak in llvm::ms_demangle::Demangler::demangleStringLiteral

2019-04-19 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14349 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Direct-leak in llvm::ms_demangle::Demangler::demangleStringLiteral https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14349#c2 http://reviews.llvm.org/rL358760 might help. -- You received this

[llvm-bugs] Issue 14386 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: StringByteSize % CharBytes == 0

2019-04-20 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14386 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: StringByteSize % CharBytes == 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14386#c2 https://reviews.llvm.org/rL358835 should fix. -- You received this message because: 1. You were

[llvm-bugs] Issue 14426 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: NumBytes > 0

2019-04-24 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14426 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: NumBytes > 0 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14426#c2 http://reviews.llvm.org/rL359109 should fix. -- You received this message because: 1. You were specifically CC'd on

[llvm-bugs] Issue 14160 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference WRITE in llvm::ms_demangle::Demangler::parse

2019-04-10 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14160 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference WRITE in llvm::ms_demangle::Demangler::parse https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14160#c2 Fix: http://reviews.llvm.org/rL358112 -- You received this message because:

[llvm-bugs] Issue 14404 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !MangledName.empty()

2019-04-22 Thread thavia monorail via llvm-bugs
Comment #2 on issue 14404 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !MangledName.empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14404#c2 http://reviews.llvm.org/rL358891 should fix. -- You received this message because: 1. You were specifically

[llvm-bugs] Issue 14201 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Stack-overflow in llvm::ms_demangle::Demangler::demangleTemplateInstantiationName

2019-07-22 Thread thavia monorail via llvm-bugs
Comment #4 on issue 14201 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Stack-overflow in llvm::ms_demangle::Demangler::demangleTemplateInstantiationName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14201#c4 The issue here is that demangleTemplateInstantiationName