public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dvyukov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55521] many instances of ASAN:SIGSEGV failures in g++ testsuite with -fsanitize=address
Date: Mon, 03 Dec 2012 04:10:00 -0000 [thread overview]
Message-ID: <bug-55521-4-xKB6CIo7ym@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55521-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55521
Dmitry Vyukov <dvyukov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dvyukov at google dot com
--- Comment #18 from Dmitry Vyukov <dvyukov at google dot com> 2012-12-03 04:08:52 UTC ---
(In reply to comment #17)
> Revised patch posted at
> http://gcc.gnu.org/ml/gcc-patches/2012-12/msg00084.html. Also tested with a
> build of xplor-nih (a complex mix of c, c++ and fortran code) which has always
> had optimization issues with FSF gcc (as xplor-nih has its own heap memory
> manager routines in fortran). A build of xplor-nih with -fsanitize=address
> produced 41 failures out of 154 tests but all of the failures emitted
> AddressSanitizer output (often unknown-crash on address) rather than
> segfaulting.
I guess it's asan signal handler transforms paging faults into "unknown-crash
on address".
But the real asan reports, do they make sense? I mean is it real bugs in user
code, or some nonsense?
next prev parent reply other threads:[~2012-12-03 4:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 21:44 [Bug sanitizer/55521] New: " howarth at nitro dot med.uc.edu
2012-11-28 21:48 ` [Bug sanitizer/55521] " howarth at nitro dot med.uc.edu
2012-11-28 21:55 ` howarth at nitro dot med.uc.edu
2012-11-28 22:16 ` howarth at nitro dot med.uc.edu
2012-11-28 22:29 ` howarth at nitro dot med.uc.edu
2012-11-29 0:47 ` howarth at nitro dot med.uc.edu
2012-11-29 21:25 ` howarth at nitro dot med.uc.edu
2012-11-30 18:01 ` howarth at nitro dot med.uc.edu
2012-12-01 1:51 ` howarth at nitro dot med.uc.edu
2012-12-01 13:55 ` jakub at gcc dot gnu.org
2012-12-01 21:37 ` howarth at nitro dot med.uc.edu
2012-12-01 21:43 ` howarth at nitro dot med.uc.edu
2012-12-01 23:27 ` howarth at nitro dot med.uc.edu
2012-12-01 23:50 ` howarth at nitro dot med.uc.edu
2012-12-01 23:51 ` howarth at nitro dot med.uc.edu
2012-12-02 2:58 ` howarth at nitro dot med.uc.edu
2012-12-02 5:38 ` howarth at nitro dot med.uc.edu
2012-12-02 21:25 ` howarth at nitro dot med.uc.edu
2012-12-03 4:10 ` dvyukov at google dot com [this message]
2012-12-04 14:53 ` howarth at nitro dot med.uc.edu
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-55521-4-xKB6CIo7ym@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).