[Bug sanitizer/56393] SIGSEGV when -fsanitize=address and dynamic lib with global objects

kcc at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Fri Feb 22 07:02:00 GMT 2013


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56393

--- Comment #19 from Kostya Serebryany <kcc at gcc dot gnu.org> 2013-02-22 07:01:51 UTC ---
In clang, static asan-rt is the default and the only option on Linux. 
(On Mac, the only option is dynamic, but that's a quite unfortunate limitation 
of the platform, it costs us quite a bit of pain during deployment).
I would also prefer to have static as the default on gcc-linux (for both asan
and tsan). 

In regular cases, when you build your own program static is what you need.

There is one case where we do need dynamic asan-rt and we build it separately:
C++ code called via SWIG from a python program. 
We already have the pre-built python binary and can not link anything to it
statically. 
But the deployment is rather painful here too, it would have been much simpler
if we could link asan-rt to python statically.



More information about the Gcc-bugs mailing list