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/61632] memory corruption in Fortran RTL when writing formatted data Date: Fri, 27 Jun 2014 22:36:00 -0000 [thread overview] Message-ID: <bug-61632-4-0vrHvAOvBY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61632-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61632 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2014-06-27 CC| |jvdelisle at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- program p call ss() call ss() end program p subroutine ss CHARACTER(3), save :: ZTYP(3) DATA ZTYP /'XXX','YYY','ZZZ'/ write(*,600,IOSTAT=iosa) 0.0,ZTYP write(*,*) 'iostat=',iosa if (iosa /= 0) print *, "error" 600 FORMAT(1PE13.5,4X,A3) end subroutine ss gives at run time [Book15] f90/bug% a.out 0.00000E+00 XXX iostat= 5006 error 0.00000E+00 XXX iostat= 5006 error which is right, but also [Book15] f90/bug% a.out 0.00000E+00 XXX iostat= 5006 error 0.00000E+00 XXX Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0x10b4c3892 #1 0x10b4c4030 #2 0x7fff8a4695a9 #3 0x10b581910 #4 0x10b58daf6 #5 0x10b58fd12 #6 0x10b58de05 #7 0x10b4b9cef #8 0x10b4b9dfb #9 0x10b4b9e34 Segmentation fault which is wrong. Note the behavior for "problem 2" is what I expect.
next prev parent reply other threads:[~2014-06-27 22:36 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-27 14:33 [Bug fortran/61632] New: " arnaud02 at users dot sourceforge.net 2014-06-27 22:36 ` dominiq at lps dot ens.fr [this message] 2014-06-28 21:20 ` [Bug fortran/61632] " dominiq at lps dot ens.fr 2014-07-12 22:12 ` jvdelisle at gcc dot gnu.org 2014-07-13 7:49 ` dominiq at lps dot ens.fr 2014-07-13 17:05 ` jvdelisle at gcc dot gnu.org 2014-07-13 21:40 ` jvdelisle at gcc dot gnu.org 2014-07-13 22:46 ` dominiq at lps dot ens.fr 2014-07-14 0:47 ` jvdelisle at gcc dot gnu.org 2014-07-14 14:27 ` [Bug fortran/61632] Memory corruption on error " dominiq at lps dot ens.fr 2014-07-14 18:30 ` dominiq at lps dot ens.fr 2014-07-15 2:22 ` jvdelisle at gcc dot gnu.org 2014-07-15 9:08 ` dominiq at lps dot ens.fr 2014-07-15 14:51 ` dominiq at lps dot ens.fr 2014-07-15 14:58 ` sgk at troutmask dot apl.washington.edu 2014-07-15 15:13 ` dominiq at lps dot ens.fr 2014-07-16 3:20 ` jvdelisle at gcc dot gnu.org 2014-07-19 3:24 ` jvdelisle at gcc dot gnu.org 2014-07-20 18:18 ` dominiq at lps dot ens.fr 2014-07-20 20:04 ` jvdelisle at gcc dot gnu.org 2014-07-25 21:51 ` jvdelisle at gcc dot gnu.org 2015-01-15 4:26 ` jvdelisle at gcc dot gnu.org 2015-02-12 0:25 ` jvdelisle 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-61632-4-0vrHvAOvBY@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).