This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Regex memory management

From: Jakub Jelinek <jakub at redhat dot com>
To: Roland McGrath <roland at redhat dot com>
Cc: Isamu Hasegawa <isamu at yamato dot ibm dot com>, Glibc hackers <libc-hacker at sources dot redhat dot com>
Date: Sun, 3 Nov 2002 06:51:43 +0100
Subject: Re: Regex memory management
References: <20021030155931.W3451@sunsite.ms.mff.cuni.cz> <200211030025.gA30P9D11901@magilla.sf.frob.com>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Sat, Nov 02, 2002 at 04:25:09PM -0800, Roland McGrath wrote:
> 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.

I can try to convert it to use obstacks, but would like to hear from Isamu
about it first...

	Jakub

References:
- Re: Regex memory management
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]