Comment #3 on issue 363 by [email protected]: Mixing instrumented and
non-instrumented runtime initializers can cause segfaults
https://code.google.com/p/address-sanitizer/issues/detail?id=363
We had same problem in GCC which uses dynamic runtime as well (see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58937). I think it eventually
got "fixed" by ensuring that libasan intercepts one of the functions called
in glibc's (or libstdc++? don't remember) initializer and lazily calling
asan_init there. Perhaps same approach could be used for OSX? BTW am I the
only one to think that inability to control initializer order is a major
disadvantage of Linux shlibs?
--
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.
