This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/63564] -fsanitize=address obscures access to free memory
- From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 16 Oct 2014 17:58:20 +0000
- Subject: [Bug sanitizer/63564] -fsanitize=address obscures access to free memory
- Auto-submitted: auto-generated
- References: <bug-63564-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63564
--- Comment #3 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
In the original example (it was ported from windows,
and the windows semaphores are completely immune
against this kind of error) the sem_post were in
*another* thread and there were several milliseconds
between the free the next malloc. So this is
already a really, really hard to find bug.
But what I don't understand, why the malloc does
*not* crash when address sanitizer is used.
The same for thread sanitizer, it does not spot
the error, and the error does not happen in debug
builds only in release builds.