[Bug sanitizer/69147] [5 Regression] Several hundred asan failures with 5.3.1 on x86_64-apple-darwin15

[chefmax at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147

--- Comment #8 from Maxim Ostapenko <chefmax at gcc dot gnu.org> ---
Eh, this is sad, let's try more. I suspect that ASan fails in MaybeReexec
function (it tries to set DYLD_INSERT_LIBRARIES env variable and reexec
itself). Dominique can I ask you two questions:

1) I'm not good in Darwin, do you use relatively new distro? If so, this may
explain why you don't observe test failures on trunk (because on new distros
dynamic linker doesn't require DYLD_INSERT_LIBRARIES to be set).

2) Could you run memcmp-1.exe with
ASAN_OPTIONS=allow_reexec=0:debug=1:verbosity=2

setenv ASAN_OPTIONS verbosity=2:debug=1:allow_reexec=0

?

(In reply to Dominique d'Humieres from comment #7)
> I have run memcmp-1.exe under lldb trying various break points from line 1
> to 12 and I always get
> 
> Process 45744 launched:
> '/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/memcmp-1.exe' (x86_64)
> ==45744==AddressSanitizer CHECK failed:
> ../../../../5_work/libsanitizer/asan/asan_malloc_mac.cc:103
> "((!asan_init_is_running)) != (0)" (0x0, 0x0)
>     <empty stack>
> 
> Process 45744 exited with status = 1 (0x00000001) 
> 
> without any backtrace available.
> 
> > Le 11 janv. 2016 à 17:20, chefmax at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> a écrit :
> > 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
> > 
> > --- Comment #6 from Maxim Ostapenko <chefmax at gcc dot gnu.org> ---
> > Ok, it seems that libasan calls some function to be intercepted while
> > AsanInitInternal still not completed. Could you try to run memcmp-1.exe under
> > gdb to provide a backtrace from failed CHECK? This way, we'll probably can
> > figure out what function was intercepted.