Comment #11 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
Maybe we should try the same hack as we do on Android?
Everything is runing with asan, but in inactivated mode.
As soon as some module calls __asan_init we activate asan.
Konstantin,
If I understood it correctly, in your proposal Asan will be activated for
any module as soon as allocation is done or some intercepted function is
called. Indeed
very soon for all active processes. That's not what we desired. The
intention was to minimize overhead by preloading asan rt only for needed
executables.
Can you specify what exactly you don't like in reexec approach? It's fair
that in dl_open case we can't rely on it. So probably we need to handle
such case separately. But in case of run-time init the executable is not
started yet and reexec shouldn't be an issue.
--
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.
