Artur Bać

Do as follows : place 2 heavy rovers on mun (made from fuel cans one with drill second with refining) Use heavy landing gear, connect it with RTS-1, click docked...

> Do you plan to add std::string overloads for most setters/constructors? It makes code usage much more convenient. It would be better to support std::string_view, it will cover any strings...

exactly @DanAlbert logcat contains only SUMARY and last line of stack where the error was finaly went into action. Does stderr can be intercepted for ordinary java with native native...

I tried asan/ubsan on xiaomi redmi 4x + lineageos 15.1 (8.1 android) - no luck , it fails with null ptr in loadlibrary it works for me only on emulator...

My wrap.sh (i build with cmake/gradle) app/src/main/resources/x86/wrap.sh ```#!/system/bin/sh HERE="$(cd "$(dirname "$0")" && pwd)" export ASAN_OPTIONS=log_to_syslog=false,allow_user_segv_handler=1,detect_stack_use_after_return=1,print_stacktrace=1 export UBSAN_OPTIONS=print_stacktrace=1 export LD_PRELOAD="$HERE/libclang_rt.asan-i686-android.so" "$@" ```

@DanAlbert You mentioned "syslog as of about that time should print to logcat." But example wrap.sh in ndk contains line log_to_syslog=false, is it correct ? cat /opt/android-ndk-r20/wrap.sh/asan.x86.sh ```#!/system/bin/sh HERE="$(cd "$(dirname...

> Could you reproduce it with a standalone binary? Works fine for me with ndk r19. I use ASAN & UBSAN only for java android app with native library

Maybe the problem with logcat stack trace is that it is to long to push it at once, and get croped to single line. When i put custom stacktrace with...

No w8. UBSAN doesn't produce full satcktrace on emulator i686, it produces only 1 stack trace line as i show. ASAN doesn't work at all on emulator x86_64, but stick...

I think i know why it doesn't work. The method described placing wrap.sh with gradle/AS in resources/lib.ARCH_name at https://developer.android.com/ndk/guides/wrap-script simply doesn't work at all on device and emulator, the wrap.sh...