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/60922] [4.9/4.10 regression] Memory leak with INTENT(OUT) CLASS argument w/ allocatable CLASS components
Date: Sun, 27 Apr 2014 13:46:00 -0000 [thread overview]
Message-ID: <bug-60922-4-NJJeexGc1O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60922-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60922
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2014-04-27
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
On x86_64-apple-darwin* I see the memory leak for all the revisions I have
tested from 4.5 to trunk. For 4.8.2 on x86_64-apple-darwin10 valgrind reports;
Iteration 1
==16277== Conditional jump or move depends on uninitialised value(s)
==16277== at 0x1000012FF: __d_vect_mod_MOD_d_vect_bld_x (pr60922.f90:118)
==16277== by 0x100001A33: MAIN__ (pr60922.f90:155)
==16277== by 0x100001A7D: main (pr60922.f90:127)
==16277== Uninitialised value was created by a stack allocation
==16277== at 0x100001115: __d_vect_mod_MOD_d_vect_bld_x (pr60922.f90:111)
==16277==
==16277== Conditional jump or move depends on uninitialised value(s)
==16277== at 0x100001309: __d_vect_mod_MOD_d_vect_bld_x (pr60922.f90:118)
==16277== by 0x100001A33: MAIN__ (pr60922.f90:155)
==16277== by 0x100001A7D: main (pr60922.f90:127)
==16277== Uninitialised value was created by a stack allocation
==16277== at 0x100001115: __d_vect_mod_MOD_d_vect_bld_x (pr60922.f90:111)
==16277==
Iteration 2
==16277==
==16277== HEAP SUMMARY:
==16277== in use at exit: 2,097,288 bytes in 3 blocks
==16277== total heap usage: 22 allocs, 19 frees, 6,295,373 bytes allocated
==16277==
==16277== 48 bytes in 1 blocks are still reachable in loss record 1 of 3
==16277== at 0x100014679: malloc (vg_replace_malloc.c:266)
==16277== by 0x10000124D: __d_vect_mod_MOD_d_vect_bld_x (pr60922.f90:116)
==16277== by 0x100001A33: MAIN__ (pr60922.f90:155)
==16277== by 0x100001A7D: main (pr60922.f90:127)
==16277==
==16277== 2,097,152 bytes in 1 blocks are still reachable in loss record 3 of 3
==16277== at 0x100014679: malloc (vg_replace_malloc.c:266)
==16277== by 0x1000016FB: __d_vect_mod_MOD_array_bld (pr60922.f90:85)
==16277== by 0x100001A0A: MAIN__ (pr60922.f90:145)
==16277== by 0x100001A7D: main (pr60922.f90:127)
==16277==
==16277== LEAK SUMMARY:
==16277== definitely lost: 0 bytes in 0 blocks
==16277== indirectly lost: 0 bytes in 0 blocks
==16277== possibly lost: 0 bytes in 0 blocks
==16277== still reachable: 2,097,200 bytes in 2 blocks
==16277== suppressed: 88 bytes in 1 blocks
==16277==
==16277== For counts of detected and suppressed errors, rerun with: -v
==16277== ERROR SUMMARY: 4 errors from 2 contexts (suppressed: 0 from 0)
next prev parent reply other threads:[~2014-04-27 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 15:33 [Bug fortran/60922] New: [4.9 " sfilippone at uniroma2 dot it
2014-04-23 7:37 ` [Bug fortran/60922] [4.9/4.10 " sfilippone at uniroma2 dot it
2014-04-23 8:41 ` rguenth at gcc dot gnu.org
2014-04-27 13:46 ` dominiq at lps dot ens.fr [this message]
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-07-17 12:28 ` sfilippone at uniroma2 dot it
2014-10-30 10:43 ` [Bug fortran/60922] [4.9/5 " jakub at gcc dot gnu.org
2015-01-16 21:28 ` janus at gcc dot gnu.org
2015-01-17 16:09 ` janus at gcc dot gnu.org
2015-01-17 16:26 ` [Bug fortran/60922] [4.9/5 regression] Memory leak with " janus at gcc dot gnu.org
2015-01-17 16:43 ` janus at gcc dot gnu.org
2015-01-17 22:07 ` janus at gcc dot gnu.org
2015-01-23 8:35 ` [Bug fortran/60922] [4.9/5 Regression] " janus at gcc dot gnu.org
2015-01-24 10:12 ` janus at gcc dot gnu.org
2015-01-24 10:14 ` janus 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-60922-4-NJJeexGc1O@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).