public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/33845] New: Namespace memory cleanup needed Date: Sat, 20 Oct 2007 22:42:00 -0000 [thread overview] Message-ID: <bug-33845-10743@http.gcc.gnu.org/bugzilla/> (raw) Valgrind gives this: ==28681== ==28681== 25,120 (14,664 direct, 10,456 indirect) bytes in 325 blocks are definitely lost in loss record 8 of 10 ==28681== at 0x4A05996: malloc (vg_replace_malloc.c:149) ==28681== by 0xB26057: xmalloc (xmalloc.c:147) ==28681== by 0x445B04: gfc_getmem (misc.c:37) ==28681== by 0x46FB99: gfc_get_namespace (symbol.c:2079) ==28681== by 0x452A43: parse_contained (parse.c:2898) ==28681== by 0x453641: gfc_parse_file (parse.c:3205) ==28681== by 0x47AF74: gfc_be_parse_file (f95-lang.c:258) ==28681== by 0x6E9181: toplev_main (toplev.c:1042) ==28681== by 0x370C61DAB3: (below main) (in /lib64/libc-2.6.so) ==28681== With argument_checking_8.f90 See: http://gcc.gnu.org/ml/fortran/2007-10/msg00296.html For the test case, need associated patch to see this. Memory issue is unrelated to the patch for PR31306. -- Summary: Namespace memory cleanup needed Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33845
next reply other threads:[~2007-10-20 22:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-20 22:42 jvdelisle at gcc dot gnu dot org [this message] 2008-03-13 14:46 ` [Bug fortran/33845] " fxcoudert at gcc dot gnu dot org 2009-03-29 7:38 ` fxcoudert at gcc dot gnu dot 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-33845-10743@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).