public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/63564] -fsanitize=address obscures access to free memory
Date: Thu, 16 Oct 2014 17:58:00 -0000	[thread overview]
Message-ID: <bug-63564-4-gvSjFAswvR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63564-4@http.gcc.gnu.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.


  parent reply	other threads:[~2014-10-16 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 17:03 [Bug sanitizer/63564] New: " bernd.edlinger at hotmail dot de
2014-10-16 17:10 ` [Bug sanitizer/63564] " jakub at gcc dot gnu.org
2014-10-16 17:11 ` kcc at gcc dot gnu.org
2014-10-16 17:58 ` bernd.edlinger at hotmail dot de [this message]
2014-10-16 18:14 ` kcc at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-63564-4-gvSjFAswvR@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).