public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: drow@mvista.com To: gcc-gnats@gcc.gnu.org Subject: c++/7612: Memory leaks in cplus-dem.c Date: Fri, 16 Aug 2002 08:06:00 -0000 [thread overview] Message-ID: <20020816130050.4275.qmail@sources.redhat.com> (raw) >Number: 7612 >Category: c++ >Synopsis: Memory leaks in cplus-dem.c >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 16 06:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: drow@mvista.com >Release: HEAD >Organization: >Environment: >Description: (Should there be a libiberty category in GNATS?) I'm tracking down some bugs in which GDB consumes excessive memory. One of them is definitely foolishness in how ofter we call the demangler, but in fixing that I've discovered that the demangler itself leaks memory. Calling cplus_demangle with DMGL_ARM | DMGL_ANSI and this string, for example: _M_get_node__t19_Rb_tree_alloc_base3Zt4pair2ZCt12basic_string3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b1i0Zt3map4Zt12basic_string3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b1i0ZsZt4less1Zt12basic_string3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b1i0Zt9allocator1ZsZt9allocator1Zt3map4Zt12basic_string3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b1i0ZsZt4less1Zt12basic_string3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b1i0Zt9allocator1Zsb1 leaks about 4K every time, above and beyond the malloc'd return value. Anyone have an idea why? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-16 13:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-16 8:06 drow [this message] 2003-03-25 1:28 bangerth 2003-03-25 2:33 drow
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=20020816130050.4275.qmail@sources.redhat.com \ --to=drow@mvista.com \ --cc=gcc-gnats@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).