Maybe we could go back to the idea of late initialization? We could teach asan allocator to handle foreign allocations in free(). Late shadow mapping seems to work OK in most cases, but if you do a whole distribution, you could hack the loader to reserve this region for you.
On Sat Nov 01 2014 at 10:21:51 PM <[email protected]> wrote: > > Comment #9 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 > > > I hate the idea of reexec (even though we have it for other use cases). > > This is too fragile and too complex. > > It surely is. On the other hand it improves usability in some very common > situation (instrument parts of large distribution) and we already have it > on other platforms. > > > Maybe you can get away with manual LD_PRELOAD and un-setting LD_PRELOAD > > for children? > > In many cases that would mean modifying source code to set/unset LD_PRELOAD > which would be a big blocker. > > -- > 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.
