public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59148] FAIL: c-c++-common/asan/strncpy-overflow-1.c  -O0  execution test on darwin13
Date: Fri, 15 Nov 2013 21:02:00 -0000	[thread overview]
Message-ID: <bug-59148-4-SA7cmoXPQC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59148-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jack Howarth <howarth at nitro dot med.uc.edu> ---
Also confirmed that if you compile the failing test case using current
llvm/clang svn with...

/sw/opt/llvm-3.4/bin/clang -fsanitize=address -g -fdiagnostics-color=never -O0
-fno-builtin-malloc -fno-builtin-strncpy -lm -m32 -o ./strncpy-overflow-1.exe
strncpy-overflow-1.c

or 

/sw/opt/llvm-3.4/bin/clang -fsanitize=address -g -fdiagnostics-color=never -O0
-fno-builtin-malloc -fno-builtin-strncpy -lm -m64 -o ./strncpy-overflow-1.exe
strncpy-overflow-1.c

that the test case fails as expected.


  parent reply	other threads:[~2013-11-15 21:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 17:08 [Bug sanitizer/59148] New: " howarth at nitro dot med.uc.edu
2013-11-15 18:43 ` [Bug sanitizer/59148] " dominiq at lps dot ens.fr
2013-11-15 21:02 ` howarth at nitro dot med.uc.edu [this message]
2013-11-21  9:43 ` glider at google dot com
2013-11-22 12:48 ` jakub at gcc dot gnu.org
2013-11-22 13:57 ` glider at google dot com
2013-11-22 21:30 ` howarth at nitro dot med.uc.edu
2014-11-19 13:54 ` [Bug sanitizer/59148] FAIL: c-c++-common/asan/strncpy-overflow-1.c -O0 execution test fxcoudert at gcc dot gnu.org
2014-11-21 23:10 ` 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-59148-4-SA7cmoXPQC@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).