https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65285
--- Comment #7 from Peter Wu <peter at lekensteyn dot nl> --- (In reply to Kostya Serebryany from comment #6) > > How does your GCC behave with the test case? The sanitizer code in GCC is > > imported from Clang, I believe, so it probably does not crash either? > > I get this: > ~/gcc-inst/bin/gcc -fsanitize=address -static-libasan d.c && ./a.out > AddressSanitizer can not describe address in more detail (wild memory access > suspected). I guess this is better than crashing. Is it possible to report something better? Can't it at least report the type and address? > Did you check the GCC trunk? It took a while to get the build environment, but now I can confirm that I see the same wild memory access error (tested with r221125).
