[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-07-23 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #19 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c19 ClusterFuzz testcase 5674959462465536 is verified as fixed, so

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-07-23 Thread ClusterFuzz-External via monorail via llvm-bugs
Comment #18 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c18 ClusterFuzz has detected this issue as fixed in range 201807110801:201807230239. Detailed report:

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-07-03 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: eney...@google.com Comment #17 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c17 (No comment was entered for this change.) -- You received this message because: 1. You were

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-06-04 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: j...@chromium.org Comment #16 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c16 (No comment was entered for this change.) -- You received this message because: 1. You were

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-05-24 Thread masc… via monorail via llvm-bugs
Comment #15 on issue 3236 by masc...@google.com: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c15 Still reproduces for me using llvm-dwarfdump-fuzzer. Note that the fuzzer uses DWARFContext::create() rather than invoking the binary

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-05-21 Thread k… via monorail via llvm-bugs
Comment #14 on issue 3236 by k...@google.com: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c14 Matt (mascasa@), please check what's going on here. -- You received this message because: 1. You were specifically CC'd on the issue You

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-05-16 Thread j… via monorail via llvm-bugs
Comment #13 on issue 3236 by j...@chromium.org: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c13 I think this is fixed. Could it be that the fuzz checker isn't working? Or running into another issue? On MacOS I get: $

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-01-12 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: xpl...@gmail.com Comment #12 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c12 (No comment was entered for this change.) -- You received this message because: 1. You were

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-01-05 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: mitchphi...@outlook.com Comment #11 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c11 (No comment was entered for this change.) -- You received this message because: 1. You

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2017-12-18 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: igm...@gmail.com Comment #10 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c10 (No comment was entered for this change.) -- You received this message because: 1. You were

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2017-12-15 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: akils...@apple.com Comment #9 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c9 (No comment was entered for this change.) -- You received this message because: 1. You were

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2017-12-11 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates: Cc: akila_sr...@apple.com Comment #8 on issue 3236 by ClusterFuzz-External: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c8 (No comment was entered for this change.) -- You received this message because: 1. You were

[llvm-bugs] Issue 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2017-10-10 Thread monor… via monorail via llvm-bugs
Updates: Cc: v...@apple.com Comment #6 on issue 3236 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c6 (No comment was entered for this change.) -- You received this