Re: [boost] [CrystaX.NET][multi_index][release] Segfaults with Clang 3.5 on Android

Subject: Re: [boost] [CrystaX.NET][multi_index][release] Segfaults with Clang 3.5 on Android
From: Dmitry Moskalchuk (dm_at_[hidden])
Date: 2015-03-20 07:12:21

> I'd like to help fixing whatever it's required (if anything) in the lib
> so as to make this work, but the existing info does not provide any clue.
> Maybe the regression tester maintainer can shed some more light here?

Reason of segfaults is not clear for me too. Call stack is very short,
having boost/multi_index_container.hpp:558 as top-level entry - for all
crashes. This makes me think call stack is corrupted for some reason.
Also, taking into account all crashes are clang-3.5 only and passed for
clang-3.4, I suspect it could be bug in clang-3.5 toolchain in our NDK.
This is not the first time I see such bugs in clang, so it probable.

I don't really think you could fix these crashes on your own, unless you
take CrystaX NDK and start debugging it on low level, fixing&rebuilding
clang if needed. Perhaps it would be more reasonable to let us debug
this issue since we're much more in context of Android specifics - and
for me it looks much more probable that bug is in clang, than in
multi_index code.

I've filed ticket https://tracker.crystax.net/issues/908 - so you can
subscribe there to easily track status changes.

-- 
Dmitry Moskalchuk