[llvm-bugs] [Bug 29006] New: Clang crashes with a std::bad_alloc exception
via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Aug 16 11:50:08 PDT 2016
https://llvm.org/bugs/show_bug.cgi?id=29006
Bug ID: 29006
Summary: Clang crashes with a std::bad_alloc exception
Product: clang
Version: 3.8
Hardware: PC
OS: Windows NT
Status: NEW
Severity: release blocker
Priority: P
Component: C++
Assignee: unassignedclangbugs at nondot.org
Reporter: markus at agoglabs.com
CC: dgregor at apple.com, llvm-bugs at lists.llvm.org
Classification: Unclassified
Created attachment 16968
--> https://llvm.org/bugs/attachment.cgi?id=16968&action=edit
Command line and cpp file causing Clang 3.8.243773 to crash
When compiling generated C++ binding code for our SkookumScript plugin for
Unreal Engine 4 using Android Codeworks 1R4u2 (which ships with Clang
3.8.243773), Clang crashes throwing a std::bad_alloc exception. I am enclosing
the generated test case code hoping you can reproduce the crash.
The same source code compiles fine with Clang 3.6, and also with Visual Studio
2015, so I am suspecting this is due to changes introduced between Clang 3.6
and 3.8.243773.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160816/fb2481e9/attachment.html>
More information about the llvm-bugs
mailing list