public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/63939] [5 Regression] Massive asan failures (356) on x86_64-apple-darwin14
Date: Tue, 18 Nov 2014 19:28:00 -0000	[thread overview]
Message-ID: <bug-63939-4-M6EHn5K36K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63939-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63939

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-11-18
     Ever confirmed|0                           |1

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The patch I have submitted is taking care of that

 =================================================================
-==25409==ERROR: AddressSanitizer: global-buffer-overflow on address 0x08049daa
at pc 0x08048717 bp 0xffe2ada8 sp 0xffe2ad9c
-READ of size 1 at 0x08049daa thread T0
-    #0 0x8048716 in main
/home/howarth/gcc-trunk/gcc/testsuite/c-c++-common/asan/global-overflow-1.c:20
-    #1 0x439383f2 in __libc_start_main (/lib/libc.so.6+0x439383f2)
-    #2 0x80485c0 
(/home/howarth/build/gcc/testsuite/gcc/global-overflow-1.exe+0x80485c0)
+==3315==ERROR: AddressSanitizer: global-buffer-overflow on address 0x0006718a
at pc 0x00066d0a bp 0xbff97748 sp 0xbff9773c
+READ of size 1 at 0x0006718a thread T0
+    #0 0x66d09 
(/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gcc/./global-overflow-1.exe+0x1d09)
+    #1 0x93b076d8  (/usr/lib/system/libdyld.dylib+0x36d8)
+    #2 0x0  (<unknown module>)


  parent reply	other threads:[~2014-11-18 19:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 17:15 [Bug testsuite/63939] New: " dominiq at lps dot ens.fr
2014-11-18 19:15 ` [Bug testsuite/63939] " howarth at bromo dot med.uc.edu
2014-11-18 19:28 ` dominiq at lps dot ens.fr [this message]
2014-11-19  9:56 ` rguenth at gcc dot gnu.org
2014-11-19 11:45 ` dominiq at lps dot ens.fr
2014-11-19 12:30 ` [Bug sanitizer/63939] [5 Regression] Massive asan failures (356) on darwin fxcoudert at gcc dot gnu.org
2014-11-19 12:34 ` jakub at gcc dot gnu.org
2014-11-19 12:35 ` jakub at gcc dot gnu.org
2014-11-19 12:43 ` fxcoudert at gcc dot gnu.org
2014-11-19 12:50 ` jakub at gcc dot gnu.org
2014-11-19 13:51 ` fxcoudert at gcc dot gnu.org
2014-11-19 14:33 ` iains at gcc dot gnu.org
2014-11-19 14:36 ` fxcoudert at gcc dot gnu.org
2014-11-19 14:53 ` dominiq at lps dot ens.fr
2014-11-19 15:27 ` fxcoudert at gcc dot gnu.org
2014-11-19 17:46 ` dominiq at lps dot ens.fr
2014-11-19 17:47 ` dominiq at lps dot ens.fr
2014-11-19 21:32 ` fxcoudert at gcc dot gnu.org
2014-11-19 22:07 ` fxcoudert at gcc dot gnu.org
2014-11-19 22:18 ` howarth at bromo dot med.uc.edu
2014-11-19 22:23 ` fxcoudert at gcc dot gnu.org
2014-11-19 22:34 ` fxcoudert at gcc dot gnu.org
2014-11-19 22:39 ` fxcoudert at gcc dot gnu.org
2014-11-20  0:31 ` howarth at bromo dot med.uc.edu
2014-11-20  1:00 ` dominiq at lps dot ens.fr
2014-11-20  1:06 ` howarth at bromo dot med.uc.edu
2014-11-21 23:17 ` dominiq at lps dot ens.fr

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-63939-4-M6EHn5K36K@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).