[llvm-bugs] Issue 3219 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor

2017-10-24 Thread monor… via monorail via llvm-bugs
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #8 on issue 3219 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c8

[llvm-bugs] Issue 3219 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor

2017-10-24 Thread monor… via monorail via llvm-bugs
Comment #7 on issue 3219 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c7 ClusterFuzz has detected this issue as fixed in range

[llvm-bugs] Issue 3219 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor

2017-10-23 Thread v… via monorail via llvm-bugs
Comment #6 on issue 3219 by v...@apple.com: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c6 Fixed in r316357. The issue was in llvm 5.0. The root cause was a bug in Wasm object file parsing. -- You received

[llvm-bugs] Issue 3219 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor

2017-10-10 Thread monor… via monorail via llvm-bugs
Updates: Cc: v...@apple.com Comment #5 on issue 3219 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c5 (No comment was entered for this change.)