public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <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 21:22:00 -0000 [thread overview] Message-ID: <bug-60038-4-kfD05WZD2w@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 #13 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Jakub Jelinek from comment #9) > Created attachment 32021 [details] > gcc49-pr60038.patch > > This seems to work for me on glibc 2.17, Uros, can you please try it on your > CentOS 5? The patch was bootstrapped and regression tested OK [1] on CentOS 5.10. [1] http://gcc.gnu.org/ml/gcc-testresults/2014-02/msg00160.html >From gcc-bugs-return-442450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Feb 03 21:39:39 2014 Return-Path: <gcc-bugs-return-442450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 11873 invoked by alias); 3 Feb 2014 21:39:38 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 11838 invoked by uid 48); 3 Feb 2014 21:39:34 -0000 From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60041] Strange behavior Date: Mon, 03 Feb 2014 21:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-60041-4-SjcbIExyDF@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60041-4@http.gcc.gnu.org/bugzilla/> References: <bug-60041-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg00207.txt.bz2 Content-length: 508 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`041 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The code is wildly undefined as the pointers are not initialized so closing as invalid.
next prev parent reply other threads:[~2014-02-03 21:22 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 ` [Bug sanitizer/60038] " kcc at gcc dot gnu.org 2014-02-03 8:26 ` 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 [this message] 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-kfD05WZD2w@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: linkBe 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).