From: Roland McGrath <roland@redhat.com>
To: Isamu Hasegawa <isamu@yamato.ibm.com>
Cc: "Jakub Jelinek <jakub@redhat.com> Glibc hackers"
<libc-hacker@sources.redhat.com>
Subject: Re: Regex memory management
Date: Sat, 02 Nov 2002 16:25:00 -0000 [thread overview]
Message-ID: <200211030025.gA30P9D11901@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Wednesday, 30 October 2002 15:59:31 +0100 <20021030155931.W3451@sunsite.ms.mff.cuni.cz>
We really should have the regex code audited for possible memory leaks in
error conditions, since Jakub has already observed some. If Isamu doesn't
have time, perhaps someone else can find time to do it soon. Jakub's
obstack suggestions sound good to me, and converting to that makes it
vastly easier to be sure the code is correct. But I don't know the regex
code and its allocation properties at all, so as to say that the obstack
model fits acceptably right in all cases.
next prev parent reply other threads:[~2002-11-03 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 7:56 Jakub Jelinek
2002-11-02 16:25 ` Roland McGrath [this message]
2002-11-02 21:52 ` Jakub Jelinek
2002-11-02 16:26 ` Roland McGrath
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=200211030025.gA30P9D11901@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=isamu@yamato.ibm.com \
--cc=libc-hacker@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).