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 sanitizer/63939] [5 Regression] Massive asan failures (356) on darwin
Date: Wed, 19 Nov 2014 17:46:00 -0000	[thread overview]
Message-ID: <bug-63939-4-M5je7T2m1r@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

--- Comment #14 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> (1) I don't understand what has changed to explain the failures.

I still don't know what change between r217514 and r217602 caused it but the
reason is that there is now two spaces instead of one in the outputs of the
kind:

#0 0x66d09  ( ...

Thus the failures are gone if the original pattern '\[(\])' is replaced with '
\[(\])'. In order to keep some backward compatibility I have replaced '\[(\])'
with ' ?\[(\])' and the failures are gone (I'll attach a new patch ASAP).

> I got the latest LLVM here: http://llvm.org/releases/download.html#3.5
> (Clang for Darwin 10.9) and put llvm-symbolizer in my PATH.

Thanks for the pointer.

> With that, and with my patch under review
> (https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02465.html),
> I am down to one failure: strncpy-overflow-1.c

Try

--- ../_clean/gcc/testsuite/c-c++-common/asan/strncpy-overflow-1.c   
2014-05-10 23:12:04.000000000 +0200
+++ gcc/testsuite/c-c++-common/asan/strncpy-overflow-1.c    2014-11-19
16:38:31.000000000 +0100
@@ -1,5 +1,6 @@
 /* { dg-do run } */
 /* { dg-options "-fno-builtin-malloc -fno-builtin-strncpy" } */
+/* { dg-additional-options "-D_FORTIFY_SOURCE=0" { target *-*-darwin* } } */
 /* { dg-shouldfail "asan" } */

 #include <string.h>


  parent reply	other threads:[~2014-11-19 17:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 17:15 [Bug testsuite/63939] New: [5 Regression] Massive asan failures (356) on x86_64-apple-darwin14 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
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 [this message]
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-M5je7T2m1r@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).