public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/31538] New: result_in_spec_1.f90: Invalid write Date: Wed, 11 Apr 2007 15:08:00 -0000 [thread overview] Message-ID: <bug-31538-13404@http.gcc.gnu.org/bugzilla/> (raw) The line 23 of gfortran.dg/result_in_spec_1.f90 (PR 31215) contains r(:)(i:i) = achar(mod(i,32)+iachar('@')) With glibc's MALLOC_CHECK_=2 the program simply segfaults. Running the test case using valgrind gives the following error: ==12576== Invalid write of size 1 ==12576== at 0x4C23DD7: memmove (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==12576== by 0x400ACF: __test1__test2 (result_in_spec_1.f90:23) ==12576== by 0x4011D1: myfunc.1445 (result_in_spec_1.f90:42) ==12576== by 0x400E9B: MAIN__ (result_in_spec_1.f90:35) ==12576== by 0x4014EB: main (fmain.c:22) ==12576== Address 0x404E8BE is 0 bytes after a block of size 6 alloc'd ==12576== at 0x4C22D06: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==12576== by 0x4E3ED38: _gfortrani_get_mem (memory.c:53) ==12576== by 0x40119F: myfunc.1445 (result_in_spec_1.f90:42) ==12576== by 0x400E9B: MAIN__ (result_in_spec_1.f90:35) ==12576== by 0x4014EB: main (fmain.c:22) -- Summary: result_in_spec_1.f90: Invalid write Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31538
next reply other threads:[~2007-04-11 15:08 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-11 15:08 burnus at gcc dot gnu dot org [this message] 2007-04-11 19:26 ` [Bug fortran/31538] " burnus at gcc dot gnu dot org 2007-04-11 20:05 ` paulthomas2 at wanadoo dot fr 2007-04-11 21:48 ` pault at gcc dot gnu dot org 2007-04-11 21:53 ` [Bug fortran/31538] misleading bounds check error pault at gcc dot gnu dot org 2007-08-10 9:43 ` burnus at gcc dot gnu dot org 2010-04-16 16:05 ` kargl at gcc dot gnu dot org 2010-04-16 16:14 ` kargl at gcc dot gnu dot org 2010-04-16 17:25 ` burnus at gcc dot gnu dot org 2010-04-16 17:39 ` dominiq at lps dot ens dot fr 2010-04-16 18:26 ` kargl at gcc dot gnu dot org 2010-04-17 21:06 ` kargl at gcc dot gnu dot org 2010-04-17 22:13 ` kargl at gcc dot gnu dot org 2010-04-17 22:22 ` kargl at gcc dot gnu dot 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-31538-13404@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).