>> I don't think that REAL() currently checks anything: > > REAL doesn't check anything. Some interceptors do the checks
That's what I meant to say - instead or relying on interceptors (I'm pretty sure we missed something out or may miss in future), just check it directly in REAL(). >> Are you sure? I don't see any ctors in compiler-rt trunk: > > The compiler eimits a CTOR function that call __asan_init Is this one coming from asan_preinit? What about unsanitized executable with preloaded ASan runtime? My proposal was to add ctor directly to ASan runtime. > First, debug output concerns only developers, not (most) users. Well, debug output is the first thing people will check when something goes wrong with ASan DSO will stop working for them so I think it makes sense to give some hints. > Second, what does this output mean? > I suspect that this means the same thing as with -static-libstdc++ -- asan > failed to intercept one of the functions is wants to intercept. Not really, it's the idiosyncrasy of Linux ld.so which resolves intercepted symbols to PLT entries in main executable instead of ASan interceptors. These warnings are really spurious and misleading (please refer to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58680 for more details). -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.
