public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55469] memory leak on read with istat.ne.0 Date: Mon, 26 Nov 2012 10:24:00 -0000 [thread overview] Message-ID: <bug-55469-4-ikzBMl2ggj@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 #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-11-26 10:23:54 UTC --- Didn't help. The following should work. The crucial part is "free_line". At a glance free_saved(dtp) (here and in comment 2) seems also to be sensible, but one should read through the file to check that it is indeed correct - and to find other places where free_line is missing. --- a/libgfortran/io/list_read.c +++ b/libgfortran/io/list_read.c @@ -1757,8 +1757,9 @@ read_real (st_parameter_dt *dtp, void * dest, int length) bad_real: + free_line (dtp); + free_saved (dtp); if (nml_bad_return (dtp, c)) return; - free_saved (dtp); if (c == EOF) {
next prev parent reply other threads:[~2012-11-26 10:24 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 [this message] 2012-11-28 14:58 ` matthias.krack at gmail dot com 2012-11-29 10:16 ` matthias.krack at gmail dot com 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-ikzBMl2ggj@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).