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

Ivan Koldaev pixus.ru at gmail.com
Fri Mar 11 23:18:02 UTC 2016


On Fri, Mar 11, 2016 at 1:41 PM, Rob Landley <rob at landley.net> wrote:
> 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

Rob,

I appreciate your input.
I understand that original author stepped away from the uClibc++ development,
but as I understand uClibc++ is not completely abandoned project,
since there are still commits dated 6 days ago
(https://git.uclibc.org/uClibc++/log/) by Bernhard Reutner-Fischer.
Also OpenWRT uses uClibc++ as a primary C++ library with the latest
GCC 5.2.x (luckily almost no program is using exceptions on embedded).
So if you are saying that posting to this list is not a right way to
have my patch accepted, could you please point me to the right one.
Thank you for your time.

P.S. added Bernhard Reutner-Fischer into CC, because I hope for some
movement for this patch.

-- 
Ivan Kold.


More information about the uClibc mailing list