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/57762] New: [4.9 Regression] Memory leak in gfortran.dg/class_array_7.f03 after revision 200084
Date: Sun, 30 Jun 2013 15:22:00 -0000	[thread overview]
Message-ID: <bug-57762-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57762
           Summary: [4.9 Regression] Memory leak in
                    gfortran.dg/class_array_7.f03 after revision 200084
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dominiq at lps dot ens.fr
                CC: burnus@net-b.de
              Host: x86_64-apple-darwin10
            Target: x86_64-apple-darwin10
             Build: x86_64-apple-darwin10

As said in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56596#c2, I see the
following memory leak under valgrind --leak-check=full

==47095== HEAP SUMMARY:
==47095==     in use at exit: 168 bytes in 2 blocks
==47095==   total heap usage: 25 allocs, 23 frees, 7,125 bytes allocated
==47095== 
==47095== 80 bytes in 1 blocks are definitely lost in loss record 1 of 2
==47095==    at 0x100013679: malloc (vg_replace_malloc.c:266)
==47095==    by 0x100001378: __realloc_MOD_reallocate (class_array_7.f03:31)
==47095==    by 0x1000019E6: MAIN__ (class_array_7.f03:55)
==47095==    by 0x100001B7B: main (class_array_7.f03:49)
==47095== 
==47095== LEAK SUMMARY:
==47095==    definitely lost: 80 bytes in 1 blocks
==47095==    indirectly lost: 0 bytes in 0 blocks
==47095==      possibly lost: 0 bytes in 0 blocks
==47095==    still reachable: 0 bytes in 0 blocks
==47095==         suppressed: 88 bytes in 1 blocks
==47095== 
==47095== For counts of detected and suppressed errors, rerun with: -v
==47095== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

starting at revision 200085 (no leak at r200083).

Note that I messed up the bracketing in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56596#c3


             reply	other threads:[~2013-06-30 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 15:22 dominiq at lps dot ens.fr [this message]
2013-07-02  9:20 ` [Bug fortran/57762] " burnus at gcc dot gnu.org
2013-07-02  9:43 ` dominiq at lps dot ens.fr
2013-07-22 11:03 ` janus at gcc dot gnu.org
2013-07-22 17:05 ` burnus at gcc dot gnu.org
2013-07-22 17:05 ` 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-57762-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).