Comment #1 on issue 332 by [email protected]: [Windows] Revisit how the
RTL handles multi-module apps
http://code.google.com/p/address-sanitizer/issues/detail?id=332
I think this is a fantastic idea!
The location at which DLLs are looked up on Windows is documented here:
<http://msdn.microsoft.com/en-us/library/windows/desktop/ms682586%28v=vs.85%29.aspx>.
The only way that I'm aware of that you could alter that search order by
embedding something in the binaries is through embedding a manifest as a
resource, but that gets a bit tricky if the application already has a
manifest. There is a tool called mt.exe
<http://msdn.microsoft.com/en-us/library/aa375649%28v=vs.85%29.aspx> which
is apparently capable of extracting a manifest from one binary, merge
another manifest inside it, and put it back into the binary (see the
-updateresource and -manifest arguments).
Honestly I don't think this trouble is worth it, because it will only work
for the cases where you invoke the linker through the compiler (which some
code bases such as Mozilla don't) and Reid's suggestion basically means
that you can get a working asan build no matter what your binaries setup
looks like by adding -fsanitize=address and copying one DLL alongside the
app, and that is a *huge* improvement over the existing setup. If that is
the best we can achieve, I would be happy!
--
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.
