[PATCH] uClibc++: any throw statement causes memory corruption

[Rob Landley]

On 03/04/2016 01:48 PM, Ivan Koldaev wrote:
> Patch for uClibc++ bug #8741 (https://bugs.busybox.net/show_bug.cgi?id=8741)
> 
> I have discovered that uClibc++ incorrectly implements C++ exception
> ABI, allocating not enough memory in the
> "__cxxabiv1::__cxa_allocate_exception":

When I spoke to Garrett Kajmowicz on the phone last month, he said that
his previous day job stuck with last GPLv2 release of gcc, so he stopped
staying up to date with changes in the C++ specification after ~2007.
Meaning he hasn't touched uClibc++ in years.

He switched jobs recently (at Google now) but didn't seem particularly
interested in picking up where he left off after a multi-year gap. (I
think they use LLVM internally there, and thus http://libcxx.llvm.org/ ?
I know Android and ChromeOS do, dunno about the web server plumbing
stuff he's dealing with. It sounded more like AI research than anything
else, really...)

I still use it in Aboriginal Linux, but only because I haven't switched
my toolchain to LLVM yet...

Rob