Could be a situation when a specific DSO was built with FORTIFY_SOURCE option. In case asan-ed binary link against that DSO, libasan can't handle the possible memory error because does not have interceptors for spinrtf_chk, snprintf_chk, vprintf_chk, vsnprintf_chk, __fprintf_chk functions.
Thanks, I've fixed that.
IMHO, in this test case the DSO is building without ASan's instrumentation, therefore the memory on the stack could not be "poisoned" with "redzones", in this case ASan could not handle the error. Sorry if I miss something, please correct me if I'm wrong. Thanks.