public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55341] address-sanitizer and Fortran Date: Wed, 19 Dec 2012 08:43:00 -0000 [thread overview] Message-ID: <bug-55341-4-5HswzsAF6x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55341-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55341 --- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-19 08:42:40 UTC --- (In reply to comment #16) > After testing on CP2K, I believe that ASAN yields a false positive (current > trunk). It is obviously hard to be sure, but the indications are > > First, the code and testcase runs without error with valgrind (when compiled > without -fsanitize=address). Those are very weak indications. Valgrind doesn't report out of bounds array accesses on the stack and similar errors (unless they are uninitialized stack area reads + use of that uninitialized data), asan does. > Second, the error happens after the last statement in the subroutine and is of > 'unknown' type > Third, the invalid write has size 1, which is a very unusual length in Fortran, > as almost no data types have that length. And this is no reason at all, for most string/memory intrinsics asan instruments them just by pretending they are writes (resp. reads or both) from the first and last byte of the area, i.e. with size 1. The backtrace clearly shows that it is memset.
next prev parent reply other threads:[~2012-12-19 8:43 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-15 13:18 [Bug fortran/55341] New: " Joost.VandeVondele at mat dot ethz.ch 2012-11-15 14:03 ` [Bug fortran/55341] " Joost.VandeVondele at mat dot ethz.ch 2012-11-16 10:28 ` janus at gcc dot gnu.org 2012-11-16 10:54 ` jakub at gcc dot gnu.org 2012-11-16 10:56 ` jakub at gcc dot gnu.org 2012-11-17 12:16 ` janus at gcc dot gnu.org 2012-11-17 13:03 ` jakub at gcc dot gnu.org 2012-12-10 12:37 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-10 12:45 ` kcc at gcc dot gnu.org 2012-12-10 13:19 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-10 13:21 ` kcc at gcc dot gnu.org 2012-12-10 13:26 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-10 13:28 ` kcc at gcc dot gnu.org 2012-12-10 13:33 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-10 13:41 ` jakub at gcc dot gnu.org 2012-12-10 13:56 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 8:17 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 8:37 ` kcc at gcc dot gnu.org 2012-12-19 8:43 ` jakub at gcc dot gnu.org [this message] 2012-12-19 8:49 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 8:52 ` kcc at gcc dot gnu.org 2012-12-19 8:53 ` jakub at gcc dot gnu.org 2012-12-19 8:59 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 9:03 ` jakub at gcc dot gnu.org 2012-12-19 9:06 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 10:32 ` kcc at gcc dot gnu.org 2012-12-19 14:10 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 14:29 ` kcc at gcc dot gnu.org 2012-12-19 14:33 ` jakub at gcc dot gnu.org 2012-12-19 14:36 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 15:57 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 16:08 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 18:01 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-19 20:59 ` howarth at nitro dot med.uc.edu 2012-12-20 16:15 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-20 16:42 ` howarth at nitro dot med.uc.edu 2012-12-20 17:31 ` hjl.tools at gmail dot com 2012-12-20 17:42 ` howarth at nitro dot med.uc.edu 2012-12-20 17:50 ` hjl.tools at gmail dot com 2012-12-21 8:02 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-21 8:04 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-21 8:11 ` kcc at gcc dot gnu.org 2012-12-21 8:19 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-21 8:23 ` kcc at gcc dot gnu.org 2012-12-22 20:54 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-23 7:44 ` kcc at gcc dot gnu.org 2012-12-23 19:45 ` Joost.VandeVondele at mat dot ethz.ch 2012-12-24 11:54 ` Joost.VandeVondele at mat dot ethz.ch 2013-01-08 17:02 ` jakub at gcc dot gnu.org 2013-01-08 17:17 ` jakub at gcc dot gnu.org 2013-01-08 17:26 ` Joost.VandeVondele at mat dot ethz.ch
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-55341-4-5HswzsAF6x@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).