Perhaps. What would be the condition for reexec? I assume we would detect (somehow) that symbol interposition for interceptors is not right, or we simply fail to map shadow.
There are other things to be mindful for. For example, on Android default SELinux policy forbids the Zygote process to execute itself. I don't think we can detect that, so we should at least have a flag in ASAN_OPTIONS disabling reexec. On Fri Nov 14 2014 at 11:56:28 AM <[email protected]> wrote: > > Comment #16 on issue 330 by [email protected]: Support re-exec of > sanitized executable with preloading libasan on Linux and Android > https://code.google.com/p/address-sanitizer/issues/detail?id=330 > > After some modification the start_deactivated flag works in our case. I've > submitted changes I applied for review http://reviews.llvm.org/D6265. > Regarding redzones - as I see in asan_rtl.cc and asan_activation.cc redzone > and max_redzone values are set to 16 in deactivated mode. Does it mean > there are still small redzones allocated for heap memory? > > I still wonder about Reexec. In current design MaybeReexec part of Asan > runtime is not Mac-specific. But it is implemented only for Mac. I think > ReExec maybe useful feature on Linux as well if we fix dlopen case. What do > you think? > > -- > You received this message because this project is configured to send all > issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings > > -- > You received this message because you are subscribed to the Google Groups > "address-sanitizer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
