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/108924] New: memory leak in doloop_warn Date: Fri, 24 Feb 2023 12:31:42 +0000 [thread overview] Message-ID: <bug-108924-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108924 Bug ID: 108924 Summary: memory leak in doloop_warn 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== 16 bytes in 2 blocks are definitely lost in loss record 6 of 2,309 ==8747== at 0x4C346A4: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==8747== by 0x5697698: __gmp_default_allocate (in /usr/lib64/libgmp.so.10.3.2) ==8747== by 0x56A7A22: __gmpz_init_set (in /usr/lib64/libgmp.so.10.3.2) ==8747== by 0x874110: do_subscript (frontend-passes.cc:2863) ==8747== by 0x874110: do_function(gfc_expr**, int*, void*) (frontend-passes.cc:2710) ==8747== by 0x870675: gfc_expr_walker(gfc_expr**, int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5243) ==8747== by 0x870859: gfc_expr_walker(gfc_expr**, int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5250) ==8747== by 0x870859: gfc_expr_walker(gfc_expr**, int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5250) ==8747== by 0x8727D9: gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5680) ==8747== by 0x872857: gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5687) ==8747== by 0x872857: gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5687) ==8747== by 0x872857: gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5687) ==8747== by 0x8738CB: doloop_warn(gfc_namespace*) (frontend-passes.cc:3079) so it looks like some gmp vars are not released.
next reply other threads:[~2023-02-24 12:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-24 12:31 rguenth at gcc dot gnu.org [this message] 2023-02-24 16:37 ` [Bug fortran/108924] " anlauf at gcc dot gnu.org 2023-02-24 20:30 ` cvs-commit at gcc dot gnu.org 2023-02-24 20:39 ` anlauf at gcc dot gnu.org 2023-03-03 14:04 ` rguenth 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-108924-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: linkBe 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).