Elliott Hughes
Elliott Hughes
yeah, i've long though this too. (and right now i'm trying to not break anything, plus i'm waiting for some long builds, so...) i've sent a patch to the mailing...
"hello, i'll be your macOS test monkey for today..." i think no surprises with the original tar file, because we were expecting this to untar fine on macOS: ``` /tmp$...
@eugenis
the `log_to_syslog=false` is in the canonical docs too: https://github.com/google/sanitizers/wiki/AddressSanitizerOnAndroid @eugenis --- do you remember the reason for this? should we just delete this from both places, since it seems like...
what version of Studio are you using?
the Studio folks tell me i got the docs wrong... apparently although it will show up as "libs.x86" under resources, it should actually be resources/libs/x86 on disk. here's my suggested...
does ``` LD_PRELOAD="$HERE/libclang_rt.asan-i686-android.so" exec "$@" ``` instead of ``` LD_PRELOAD="$HERE/libclang_rt.asan-i686-android.so" "$@" ``` fix the tag? @eugenis should be able to answer the question about the escape sequences...
i know @yabinc had this working (for the platform) at one point, but it may have bitrotted. @eugenis might also know something useful...
yeah, we've had a prototype for a while, and this is the reason we left a hole in the dynamic linker's native library namespace so that apps can access icu4c...
> it looks you are going to ship a copy of icu4c no. the prototype uses dlsym to find the system implementations.