public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/63939] [5 Regression] Massive asan failures (356) on darwin Date: Thu, 20 Nov 2014 00:31:00 -0000 [thread overview] Message-ID: <bug-63939-4-QM4cPxFxby@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 #22 from howarth at bromo dot med.uc.edu --- At r217817 on x86_64-apple-darwin14, without llvm-symbolizer in the path but with https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63534#c50 applied, I still see failures for... FAIL: c-c++-common/asan/null-deref-1.c -O1 output pattern test, is ASAN:SIGSEGV FAIL: c-c++-common/asan/null-deref-1.c -O2 output pattern test, is ASAN:SIGSEGV FAIL: c-c++-common/asan/null-deref-1.c -O3 -fomit-frame-pointer output pattern test, is ASAN:SIGSEGV FAIL: c-c++-common/asan/null-deref-1.c -O3 -g output pattern test, is ASAN:SIGSEGV FAIL: c-c++-common/asan/null-deref-1.c -Os output pattern test, is ASAN:SIGSEGV FAIL: c-c++-common/asan/null-deref-1.c -O2 -flto -flto-partition=none output pattern test, is ASAN:SIGSEGV FAIL: c-c++-common/asan/null-deref-1.c -O2 -flto output pattern test, is ASAN:SIGSEGV as well as the unpatched c-c++-common/asan/strlen-overflow-1.c failures.
next prev parent reply other threads:[~2014-11-20 0:31 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 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 [this message] 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-QM4cPxFxby@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).