https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98669
--- Comment #4 from Matthias Klose <doko at debian dot org> ---
$ /usr/lib/gcc-snapshot/bin/gcc -fsanitize=address crypt.c -lcrypt &&
LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib ./a.out
sasWQy9ecMDEs
looks like this happens with a compiler configured with --enable-default-pie.
Otoh, I still see:
$ gcc-10 -no-pie -fno-stack-protector -fsanitize=address crypt.c -lcrypt &&
./a.out
AddressSanitizer:DEADLYSIGNAL
=================================================================
==2831466==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc
0x000000000000 bp 0x7ffd02382710 sp 0x7ffd023826f8 T0)
==2831466==Hint: pc points to the zero page.
==2831466==The signal is caused by a READ memory access.
==2831466==Hint: address points to the zero page.
#0 0x0 (<unknown module>)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (<unknown module>)
==2831466==ABORTING
