public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/62132] [5 Regression] FAIL: c-c++-common/asan/misalign-[12].c after r213807 on x86_64-apple-darwin13 with -m32
Date: Wed, 20 Aug 2014 08:51:00 -0000 [thread overview]
Message-ID: <bug-62132-4-oeBMVYvWRr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62132-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62132
Yury Gribov <y.gribov at samsung dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |y.gribov at samsung dot com
--- Comment #1 from Yury Gribov <y.gribov at samsung dot com> ---
I can confirm this but I'm not sure that this has anything to do with r213806
(besides it triggering already existing problem). Libasan uses frame pointers
unconditionally to unwind stack on Darwin. By default 32-bit Darwins seem to
use -fomit-frame-pointer so unwinding can (and in our case does) fail. Adding
-fno-omit-frame-pointer to compile options fixed the problem for me. Perhaps we
should add this flag by default when running Asan tests on Darwin? Or maybe
libsanitizer could be updated to unwind with fp?
next prev parent reply other threads:[~2014-08-20 8:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:49 [Bug sanitizer/62132] New: [5.0 " dominiq at lps dot ens.fr
2014-08-14 9:04 ` [Bug sanitizer/62132] " rguenth at gcc dot gnu.org
2014-08-20 8:51 ` y.gribov at samsung dot com [this message]
2014-08-20 9:24 ` [Bug sanitizer/62132] [5 " y.gribov at samsung dot com
2014-08-20 9:34 ` dominiq at lps dot ens.fr
2014-08-20 9:45 ` y.gribov at samsung dot com
2014-08-20 10:33 ` iains at gcc dot gnu.org
2014-08-20 13:58 ` y.gribov at samsung dot com
2014-09-14 17:22 ` dominiq at lps dot ens.fr
2014-11-06 13:11 ` dominiq at lps dot ens.fr
2014-11-06 13:17 ` y.gribov at samsung dot com
2014-11-08 14:28 ` iains at gcc dot gnu.org
2014-11-11 12:02 ` dominiq at lps dot ens.fr
2014-11-18 15:05 ` jakub at gcc dot gnu.org
2014-11-19 14:04 ` rguenth at gcc dot gnu.org
2014-11-19 14:12 ` dominiq at lps dot ens.fr
2014-11-19 14:30 ` fxcoudert at gcc dot gnu.org
2014-11-19 14:32 ` fxcoudert at gcc dot gnu.org
2014-11-19 14:37 ` fxcoudert at gcc dot gnu.org
2014-11-19 14:46 ` iains at gcc dot gnu.org
2014-11-20 11:07 ` fxcoudert 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-62132-4-oeBMVYvWRr@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).