This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/56491] [OOP] Memory leak with vtab's type-bound-procedures
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 04 Aug 2018 11:20:26 +0000
- Subject: [Bug fortran/56491] [OOP] Memory leak with vtab's type-bound-procedures
- Auto-submitted: auto-generated
- References: <bug-56491-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56491
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks|86754 |68800
--- Comment #3 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #2)
> On darwin10, r208594, I get
>
> ==84656== 4 bytes in 1 blocks are definitely lost in loss record 1 of 2
> ==84656== at 0x100012679: malloc (vg_replace_malloc.c:266)
> ==84656== by 0x100000C90: MAIN__ (in ./a.out)
> ==84656== by 0x100000D87: main (in ./a.out)
Dominique, you're running valgrind on a.out; Tobias was running it on
gfortran/f951.
This PR is concerned with compile-time leaks, not run-time leaks, therefore it
should not block PR 86754, but rather PR 68800.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68800
[Bug 68800] Fortran FE produces many memory leaks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86754
[Bug 86754] [meta-bug] Memory leaks at run time