Comment #2 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
If only a single shared library in the testing environment is
instrumented (and
depends on the ASan runtime library), and the main executable is not,
__asan_init() is going to be called only at the moment that library is
loaded
(including the case when we use dlopen() to load it).
Right, explicitly banning the dlopen case would be nice but I'm not sure
how to achieve this.
At that moment the main
executable might have done a fair amount of work which we can't simply
replay
upon reexec().
If main executable depends on the library (which is really the case we are
interested in) then worst-case some library initializers might have been
executed.
I believe that unless the main executable depends on the ASan shared
runtime the > users must explicitly preload the runtime in order to test
any pieces of code
that might initialize late.
This may get hard to do for some systems. Finding the exact place where a
particular executable(s) depending on a library in a large autobuilt
distribution is challenging.
--
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.
