This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/65285] __asan_describe_address crashes when used with global variable
- From: "peter at lekensteyn dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 03 Mar 2015 23:49:06 +0000
- Subject: [Bug sanitizer/65285] __asan_describe_address crashes when used with global variable
- Auto-submitted: auto-generated
- References: <bug-65285-4 at http dot gcc dot gnu dot org/bugzilla/>
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).