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/56596] Invalid read of size 4 gfortran.dg/class_array_7.f03 Date: Thu, 27 Jun 2013 21:46:00 -0000 [thread overview] Message-ID: <bug-56596-4-jVVTg5K5fk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56596-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56596 --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- This seems to have been fixed between revision 199435 (2013-05-30) and revision 199885 (2013-06-03): revision 199528? The error ==15298== 80 bytes in 1 blocks are definitely lost in loss record 1 of 2 ==15298== at 0x100013679: malloc (vg_replace_malloc.c:266) ==15298== by 0x100001358: __realloc_MOD_reallocate (class_array_7.f03:31) ==15298== by 0x1000019C6: MAIN__ (class_array_7.f03:55) ==15298== by 0x100001B5B: main (class_array_7.f03:49) appeared between revisions 200350 (2013-06-23) with the patch of revision 200361 and a clean revision 200361 (2013-06-24). Could it be caused by revision 200360?
next prev parent reply other threads:[~2013-06-27 21:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-11 13:54 [Bug fortran/56596] New: " dominiq at lps dot ens.fr 2013-03-13 14:18 ` [Bug fortran/56596] " janus at gcc dot gnu.org 2013-06-27 10:00 ` dominiq at lps dot ens.fr 2013-06-27 21:46 ` dominiq at lps dot ens.fr [this message] 2013-06-28 7:10 ` burnus at gcc dot gnu.org 2013-06-29 22:07 ` dominiq at lps dot ens.fr 2013-06-30 15:25 ` 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-56596-4-jVVTg5K5fk@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).