Thanks guys, gcc48 worked a charm.
For our use case, the DSO is the only option. A third party application which cannot be recompiled with the required flags, internal teams developing DSOs and trying to get to the bottom of some stack smashing. Thanks, mjoc On Thursday, 6 February 2014 10:05:40 UTC, kcc wrote: > > > > > On Thu, Feb 6, 2014 at 1:59 PM, Yuri Gribov <[email protected]<javascript:> > > wrote: > >> > but I don't want to do this unless we know that someone really needs it >> > and this is the right way to solve some problem. >> >> Some benefits of dynamic runtime: >> 1) reduced memory overhead (important for embedded world) >> 2) it's also rather handy when you have a bunch of apps and libs some >> of which are sanitized and some aren't (in real world you don't always >> have the luxury of full app rebuild); LD_PRELOAD would allow you to >> override malloc and friends and enable ASan even in that case >> > There is no disagreement here. > Note that the only way ASAN is used on Android, Mac and iOS (and Windows?) > is through dynamic run-time. > But: we are using dynamic run-time for python in one of our settings > and the experience is so painful that we don't want to advertise > asan-as-dso on Linux, > where static run-time works well for the majority of use cases. > There are some bugs specific to using asan as a shared library, e.g. > https://code.google.com/p/address-sanitizer/issues/detail?id=147 > > --kcc > > >> >> -Y >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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/groups/opt_out.
