public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64986] New: class_to_type_4.f90: valgrind error: Invalid read/write of size 8
Date: Mon, 09 Feb 2015 18:29:00 -0000 [thread overview]
Message-ID: <bug-64986-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64986
Bug ID: 64986
Summary: class_to_type_4.f90: valgrind error: Invalid
read/write of size 8
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: ubizjak at gmail dot com
/ssd/uros/gcc-build/gcc/gfortran -B /ssd/uros/gcc-build/gcc -B
/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/libgfortran/ -L
/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/libgfortran/.libs/ -L
/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/libquadmath/.libs/ -O2 -g
class_to_type_4.f90
$ valgrind ./a.out
==991== Memcheck, a memory error detector
==991== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==991== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==991== Command: ./a.out
==991==
==991== Invalid read of size 8
==991== at 0x401F8F: MAIN__ (class_to_type_4.f90:58)
==991== by 0x40076C: main (class_to_type_4.f90:63)
==991== Address 0x51afcb8 is 8 bytes inside a block of size 104 free'd
==991== at 0x4A07CE9: free (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==991== by 0x401F8E: MAIN__ (class_to_type_4.f90:58)
==991== by 0x40076C: main (class_to_type_4.f90:63)
==991==
==991== Invalid write of size 8
==991== at 0x401FAB: MAIN__ (class_to_type_4.f90:58)
==991== by 0x40076C: main (class_to_type_4.f90:63)
==991== Address 0x51afcb8 is 8 bytes inside a block of size 104 free'd
==991== at 0x4A07CE9: free (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==991== by 0x401F8E: MAIN__ (class_to_type_4.f90:58)
==991== by 0x40076C: main (class_to_type_4.f90:63)
==991==
next reply other threads:[~2015-02-09 18:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 18:29 ubizjak at gmail dot com [this message]
2015-02-09 18:31 ` [Bug fortran/64986] " ubizjak at gmail dot com
2015-02-13 10:37 ` dominiq at lps dot ens.fr
2015-02-13 15:33 ` paul.richard.thomas at gmail dot com
2015-02-16 15:36 ` dominiq at lps dot ens.fr
2015-04-03 0:10 ` hp at gcc dot gnu.org
2015-04-03 10:01 ` dominiq at lps dot ens.fr
2015-04-03 12:23 ` dominiq at lps dot ens.fr
2015-04-16 5:06 ` hp at gcc dot gnu.org
2015-07-18 13:24 ` mikael at gcc dot gnu.org
2015-07-21 10:02 ` dominiq at lps dot ens.fr
2015-07-22 16:24 ` mikael at gcc dot gnu.org
2015-07-23 7:04 ` paul.richard.thomas at gmail dot com
2015-07-24 13:55 ` mikael at gcc dot gnu.org
2015-07-24 14:45 ` mikael at gcc dot gnu.org
2015-07-24 19:47 ` mikael at gcc dot gnu.org
2015-07-25 19:20 ` mikael at gcc dot gnu.org
2015-07-25 19:23 ` mikael 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-64986-4@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).