public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61775] Allocatable array initialized by implied-do loop array constructor gives invalid memory reference
Date: Thu, 10 Jul 2014 20:37:00 -0000 [thread overview]
Message-ID: <bug-61775-4-lUijpu55VN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61775-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61775
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-07-10
Ever confirmed|0 |1
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Whatever the issue was, it appears to be fixed in HEAD.
I don't think so. Could you run the test with -fsanitize=address. On
x86_64-apple-darwin13 r212433, I get at run time:
=================================================================
==4401==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000e014
at pc 0x1064f08c1 bp 0x7fff597100e0 sp 0x7fff597100d8
WRITE of size 4 at 0x60200000e014 thread T0
#0 0x1064f08c0
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x1000018c0)
#1 0x1064f0d19
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100001d19)
#2 0x7fff922ef5fc (/usr/lib/system/libdyld.dylib+0x35fc)
0x60200000e014 is located 0 bytes to the right of 4-byte region
[0x60200000e010,0x60200000e014)
allocated by thread T0 here:
#0 0x10652a4c9 (/opt/gcc/gcc4.10p-212433/lib/libasan.1.dylib+0x314c9)
#1 0x1064f0846
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100001846)
#2 0x1064f0d19
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100001d19)
#3 0x7fff922ef5fc (/usr/lib/system/libdyld.dylib+0x35fc)
SUMMARY: AddressSanitizer: heap-buffer-overflow ??:0 ??
Shadow bytes around the buggy address:
0x1c0400001bb0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001bc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001bd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001be0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001bf0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x1c0400001c00: fa fa[04]fa fa fa 06 fa fa fa 06 fa fa fa 05 fa
0x1c0400001c10: fa fa 00 fa fa fa 00 00 fa fa 03 fa fa fa 00 02
0x1c0400001c20: fa fa 00 07 fa fa 00 fa fa fa 00 00 fa fa 00 00
0x1c0400001c30: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00
0x1c0400001c40: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00
0x1c0400001c50: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
ASan internal: fe
==4401==ABORTING
next prev parent reply other threads:[~2014-07-10 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 17:02 [Bug fortran/61775] New: " robert.rosenberg at nrl dot navy.mil
2014-07-10 20:29 ` [Bug fortran/61775] " kargl at gcc dot gnu.org
2014-07-10 20:34 ` kargl at gcc dot gnu.org
2014-07-10 20:37 ` dominiq at lps dot ens.fr [this message]
2014-07-11 20:38 ` mikael at gcc dot gnu.org
2014-07-12 11:44 ` 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-61775-4-lUijpu55VN@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).