public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthias.krack at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55469] memory leak on read with istat.ne.0
Date: Thu, 29 Nov 2012 10:16:00 -0000	[thread overview]
Message-ID: <bug-55469-4-QowtKHUAbI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55469-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55469

--- Comment #5 from Matthias Krack <matthias.krack at gmail dot com> 2012-11-29 10:16:06 UTC ---
Memory leaks are still present for other choices of the string t.
For instance t="." or t="./" is still causing memory leaks for the test case in
comment 1 as detected by valgrind 3.8.1 for a patched (see comment 3) gcc
version 4.7.3 20121129 (prerelease) (GCC)

==25497== 300 bytes in 1 blocks are definitely lost in loss record 1 of 1
==25497==    at 0x4A0765C: malloc (vg_replace_malloc.c:270)
==25497==    by 0x4C29208: _gfortrani_get_mem (memory.c:43)
==25497==    by 0x4CDD799: push_char (list_read.c:78)
==25497==    by 0x4CDE892: read_real (list_read.c:1408)
==25497==    by 0x4CE0F86: _gfortrani_list_formatted_read (list_read.c:1876)

It seems that the logic for the memory cleanup is still incomplete.

Note, that the memory leaks appear only if the IOSTAT parameter is present in
the READ statement.


  parent reply	other threads:[~2012-11-29 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26  7:57 [Bug fortran/55469] New: " Joost.VandeVondele at mat dot ethz.ch
2012-11-26  8:01 ` [Bug fortran/55469] " Joost.VandeVondele at mat dot ethz.ch
2012-11-26  9:27 ` burnus at gcc dot gnu.org
2012-11-26 10:24 ` burnus at gcc dot gnu.org
2012-11-28 14:58 ` matthias.krack at gmail dot com
2012-11-29 10:16 ` matthias.krack at gmail dot com [this message]
2012-11-29 10:23 ` Joost.VandeVondele at mat dot ethz.ch
2012-11-29 11:13 ` matthias.krack at gmail dot com
2012-11-29 11:40 ` burnus at gcc dot gnu.org
2013-02-07  5:58 ` Joost.VandeVondele at mat dot ethz.ch
2013-09-24  8:03 ` Joost.VandeVondele at mat dot ethz.ch
2013-10-01 20:52 ` burnus at gcc dot gnu.org
2013-10-04 10:06 ` burnus at gcc dot gnu.org
2013-10-04 10:09 ` burnus at gcc dot gnu.org
2013-10-04 10:09 ` burnus 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-55469-4-QowtKHUAbI@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).