Control: reassign -1 libc6 2.27-1 Control: retitle -1 libc6:i386 yields invalid writes, triggered by GCC's AddressSanitizer Control: severity -1 serious
On 2018-03-05 14:10:56 +0100, Vincent Lefevre wrote: > cventin:~> cat tst.c > int main (void) > { > return 0; > } > cventin:~> gcc-snapshot -m32 -fsanitize=address tst.c -o tst > cventin:~> ./tst > AddressSanitizer:DEADLYSIGNAL > ================================================================= > ==25032==ERROR: AddressSanitizer: SEGV on unknown address 0xf7fa7e70 (pc > 0xf7fa7e84 bp 0xffbf40ac sp 0xffbf406c T16777215) > ==25032==The signal is caused by a WRITE memory access. > #0 0xf7fa7e83 in _dl_get_tls_static_info (/lib/ld-linux.so.2+0x11e83) > #1 0xf7ac147d (/usr/lib/gcc-snapshot/lib32/libasan.so.5+0x10e47d) > #2 0xf7aafd27 (/usr/lib/gcc-snapshot/lib32/libasan.so.5+0xfcd27) > #3 0xf7fa591a (/lib/ld-linux.so.2+0xf91a) > #4 0xf7f96cb9 (/lib/ld-linux.so.2+0xcb9) > > AddressSanitizer can not provide additional info. > SUMMARY: AddressSanitizer: SEGV (/lib/ld-linux.so.2+0x11e83) in > _dl_get_tls_static_info > ==25032==ABORTING libc6:i386 was actually the cause (gcc-snapshot had not changed). Reverting to 2.26-6 makes the crash disappear. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)