Artur Bać

Thats was the point on filesystem this must be located **app/src/main/resources/lib/ARCH/wrap.sh** then wrap.sh in apk is packaged with output native libs and I can confirm that i see UBSAN stacktraces...

the exec doesn't change tag from wrap.sh however its not a problem for me. To be more precise for futre readers the wrap.sh must look like below with exec in...

From my point of view we can close this FR Conclusion to source problem For gradle/cmake projects the wrap.sh must must be located on disk at **app/src/main/resources/lib/ABI/wrap.sh** where ABI means...

and toolchains/llvm/prebuilt/linux-x86_64/lib64/clang/8.0.7/bin/asan_device_setup - fixi386 ->i686 - add missing x86_64

From a an app developer who prepares tools for team. asan_device_setup has and advantage that sanitized run in emualtor is easier to prepare, doesn't need any changes to gradle config...

>Makes sense. Outside of a std::abs test case I can see very few uses for it in the real world anyway. I got problems compiling newset boost 1.67 with for...

Actualy it dosnt matter what libc++ You use as long you link staticaly to it, if your code will not use any functionality from stl it may be not linked...

@topjohnwu so the difference must come from somthing you use from stl or "stl_abi", like exception hadling code, thread_local code etc. Best will be figuring out what it is used...

You are missing the agreed fixing of documentation for use it.

I will squash it finally so You don't need to write proper commit names and messages ...