public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dreamershl at gmail dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug regex/788] New: re_comile_fastmap() will cause the 20 bytes memory leak
Date: Sun, 13 Mar 2005 05:59:00 -0000	[thread overview]
Message-ID: <20050313055935.788.dreamershl@gmail.com> (raw)

When I use the fastmap in the regex. I find the memory leak. each time it will
cost 20 bytes. I check the re_compile_fastmap(). I find it seem this function
don't release the structure "fail_stack_type" memory. In the INIT_FAIL_STACK
macro, the fail_stack will get 5* sizeof (fail_stack_elt_t) bytes memory. but I
can't find the release statement at the end of the function.

int re_compile_fastmap (struct re_pattern_buffer *bufp)
{
  fail_stack_type fail_stack;
  ...
  INIT_FAIL_STACK ();
}

-- 
           Summary: re_comile_fastmap() will cause the 20 bytes memory leak
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P1
         Component: regex
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: dreamershl at gmail dot com
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=788

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-03-13  5:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13  5:59 dreamershl at gmail dot com [this message]
2005-03-15  7:22 ` [Bug regex/788] " jakub at redhat dot com

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=20050313055935.788.dreamershl@gmail.com \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /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).