public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108925] New: memory leak of gfc_get_namespace result
Date: Fri, 24 Feb 2023 12:32:59 +0000 [thread overview]
Message-ID: <bug-108925-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108925
Bug ID: 108925
Summary: memory leak of gfc_get_namespace result
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
valgrind leak check complains
==8747== 3,976 (2,792 direct, 1,184 indirect) bytes in 1 blocks are definitely
lost in loss record 2,248 of 2,309
==8747== at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8747== by 0x1C25680: xcalloc (xmalloc.c:164)
==8747== by 0x7C998E: gfc_get_namespace(gfc_namespace*, int)
(symbol.cc:2869)
==8747== by 0x767D44: load_needed(pointer_info*) (module.cc:5175)
==8747== by 0x767BB5: load_needed(pointer_info*) (module.cc:5153)
==8747== by 0x767BB5: load_needed(pointer_info*) (module.cc:5153)
==8747== by 0x767BB5: load_needed(pointer_info*) (module.cc:5153)
==8747== by 0x767BB5: load_needed(pointer_info*) (module.cc:5153)
==8747== by 0x767BC0: load_needed(pointer_info*) (module.cc:5154)
==8747== by 0x767BC0: load_needed(pointer_info*) (module.cc:5154)
==8747== by 0x767BC0: load_needed(pointer_info*) (module.cc:5154)
==8747== by 0x767BB5: load_needed(pointer_info*) (module.cc:5153)
next reply other threads:[~2023-02-24 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 12:32 rguenth at gcc dot gnu.org [this message]
2023-03-06 19:23 ` [Bug fortran/108925] " mikael at gcc dot gnu.org
2023-03-06 19:40 ` anlauf at gcc dot gnu.org
2023-03-06 19:47 ` mikael at gcc dot gnu.org
2023-03-06 19:52 ` anlauf at gcc dot gnu.org
2023-03-06 20:00 ` mikael at gcc dot gnu.org
2023-03-07 11:41 ` mikael at gcc dot gnu.org
2023-03-08 19:52 ` anlauf 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-108925-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).