Cool! My comments below. > Smaller disk usage
How about "Smaller memory footprint"? > __asan_init is not called from preinit_array and so there is a risk that an > instrumented code will get called before __asan_init 1) Should probably decribe symptoms here (call to NULL). 2) Can we add a check to REAL() to produce a nice diagnostic message in this case? 3) We once discussed making __asan_init a constructor to solve this problem (discussion and patch available here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58937). > the binary is linked against incompatible DSO version Nice one. I wonder whether we can catch this in preloaded libasan (e.g. search for all older __asan_init_vXXX using dlsym at start). >> There are some bugs specific to using asan as a shared library, e.g. Can you add other bugs as well? Some proposal from me: * could you add a note about spurious "failed to intercept" warnings? (see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58680 for reference) BTW should we acronimize as ASAN or ASan? -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]. For more options, visit https://groups.google.com/groups/opt_out.
