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: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 01 Mar 2013 16:45:01 +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/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56491
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-01 16:45:01 UTC ---
The VTAB issue is now fixed:
http://gcc.gnu.org/ml/gcc-cvs/2013-03/msg00024.html
However, another issue is still pending:
864 (192 direct, 672 indirect) bytes in 1 blocks are definitely lost in
loss record 325 of 355
at 0x4C2A0B4: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0xED30B0: xcalloc (xmalloc.c:162)
by 0x571BBF: gfc_get_expr() (expr.c:47)
by 0x57442B: gfc_get_variable_expr(gfc_symtree*) (expr.c:3936)
by 0x5D06E2: resolve_code(gfc_code*, gfc_namespace*) (resolve.c:8536)
by 0x5D1CEE: resolve_codes(gfc_namespace*) (resolve.c:14972)
That's the following expression in resolve.c:
st->n.sym->assoc->target = gfc_get_variable_expr (code->expr1->symtree);