Closed rcdailey closed 6 years ago
Actually please allow me to close this for now. I am seeing similar crashes during stack unwinding after throwing exceptions in code not related to boost. I think this might be an NDK issue. Let me investigate some more. If I find out otherwise I'll reopen. Sorry for the confusion.
I'm using Boost 1.68. I compiled it using NDK r17b. I used the following
user-config.jam
. Note I did all of this on Windows using Command Prompt.I created the standalone toolchains for the NDK using this command:
And I built boost using this command:
When I run my native code on Android, which uses this version of boost, I get a SIGSEGV with this callstack:
The code using lexical_cast is doing, basically:
This causes a
bad_lexical_cast
to be thrown; but in the middle of throwing that exception, the segfault happens. I don't have any further analysis to share, and I'm not even certain what the root cause is. Does the information I provided offer any hints? I'm not sure if this is a bug, and I'm not sure if the lexical cast repo is the best place to ask the question since boost.exception shows up in the call stack too.