Comment #6 on issue 178 by [email protected]: Init-order checking is
dlopen-hostile
https://code.google.com/p/address-sanitizer/issues/detail?id=178
FTR the problem description provided here is a bit misleading. strict
init-order checker is *both* multithreading- and dlopen()-hostile: we can
end up with false positives both if use dlopen() in a single-threaded
program, and if we call spawn new threads during initialization, but don't
call dlopen(). That is, we need to disable init-order checker both in
pthread_create interceptor (was done in r180106) and in dlopen interceptor
(this is addressed in r230288).
--
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.
