[LLVMdev] Building sanitizers for Android

[Evgeniy Stepanov]

On Wed, Apr 23, 2014 at 9:08 AM, Yury Gribov <y.gribov at samsung.com> wrote:
>>> It's not that easy. Some tests require passing environment variables
>>
>>
>> As Evgeniy mentioned, it's a short enough list of variables that you
>> can whitelist them.  LD_PRELOAD, LD_LIBRARY_PATH, ASAN_OPTIONS, etc.
>
>
> Still sounds somewhat hacky. E.g. what if you've sanitized Clang itself and
> then run it with custom ASAN_OPTIONS?
> Surely you won't want to propagate them to ssh unless the test explicitly
> asks for them.

I think we want to propagate them anyway. We are talking of a %run
macro, which is a replacement for directly running the test binary -
if the binary would get ASAN_OPTIONS in the "normal" (native) testing
mode, we would like it to get the same ASAN_OPTIONS in the
cross-testing mode as well. We just need to filter out stuff that does
not make sense on a remote machine, like host PATH setting.

>
> -Y