public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/12567] regexec sucks up mem when used multiple times with different strings
Date: Fri, 11 Mar 2011 07:55:00 -0000 [thread overview]
Message-ID: <bug-12567-132-PEygGH1QbF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12567-132@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12567
Mike Frysinger <vapier at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
Summary|regexec leaks mem when used |regexec sucks up mem when
|multiple times |used multiple times with
| |different strings
--- Comment #2 from Mike Frysinger <vapier at gentoo dot org> 2011-03-11 07:55:05 UTC ---
being pedantic doesnt make the poor behavior go away. clearly the behavior is
highly undesirable.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-03-11 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 5:13 [Bug regex/12567] New: regexec leaks mem when used multiple times vapier at gentoo dot org
2011-03-11 5:13 ` [Bug regex/12567] " vapier at gentoo dot org
2011-03-11 6:55 ` jakub at redhat dot com
2011-03-11 7:55 ` vapier at gentoo dot org [this message]
2011-03-11 8:04 ` [Bug regex/12567] regexec sucks up mem when used multiple times with different strings jakub at redhat dot com
2011-03-11 8:10 ` bonzini at gnu dot org
2014-06-27 13:45 ` fweimer 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=bug-12567-132-PEygGH1QbF@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@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).