public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/60038] AddressSanitizer CHECK failed ... "((*tls_addr + *tls_size)) <= ((*stk_addr + *stk_size))" on CentOS 5.10
Date: Mon, 03 Feb 2014 08:19:00 -0000	[thread overview]
Message-ID: <bug-60038-4-zcDqLbHcV5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60038-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60038

--- Comment #1 from Kostya Serebryany <kcc at gcc dot gnu.org> ---
I expect this also happens with the clang version of ASAN, please confirm.

This is related to the hackish way we extract stack and tls bounds,
and CentOS 5.10 may have different version of glibc or some other difference.
What is the version of glibc on your OS?

We are trying to solve it in a general way in glibc
(https://sourceware.org/bugzilla/show_bug.cgi?id=16291),
but that will not happen for the existing distros.


  reply	other threads:[~2014-02-03  8:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03  7:53 [Bug sanitizer/60038] New: " ubizjak at gmail dot com
2014-02-03  8:19 ` kcc at gcc dot gnu.org [this message]
2014-02-03  8:26 ` [Bug sanitizer/60038] " ubizjak at gmail dot com
2014-02-03  8:33 ` kcc at gcc dot gnu.org
2014-02-03  8:47 ` jakub at gcc dot gnu.org
2014-02-03  8:53 ` jakub at gcc dot gnu.org
2014-02-03  8:56 ` kcc at gcc dot gnu.org
2014-02-03  9:26 ` jakub at gcc dot gnu.org
2014-02-03  9:27 ` ubizjak at gmail dot com
2014-02-03  9:33 ` ubizjak at gmail dot com
2014-02-03 10:00 ` ubizjak at gmail dot com
2014-02-03 21:22 ` ubizjak at gmail dot com
2014-02-04  4:18 ` kcc at gcc dot gnu.org
2014-02-04  7:38 ` jakub at gcc dot gnu.org
2014-02-04  7:42 ` jakub 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-60038-4-zcDqLbHcV5@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).