[Bug regex/215] memoryleak in regexec

folkert at vanheusden dot com sourceware-bugzilla@sources.redhat.com
Sun Jun 20 21:44:00 GMT 2004


------- Additional Comments From folkert at vanheusden dot com  2004-06-20 21:44 -------
Subject: Re:  memoryleak in regexec

I failed to do that. I've wrote a couple of testprograms doing thousands of
regexecs on data which is normally processed by multitail and those tools
never have memory leaks that keep on groing (they leak, but it is constant
leakage).
I used valgrind for all of this (-v --leak-check=yes --leak-resolution=high
--show-reachable=yes).
I've upgraded my system to 2.3.2 now (was: 2.3.1), hopefully that solved it.
If not: please give me pointers on how to start tracking all of this (debian
system).

On 11 Jun 2004, gotom at debian dot or
dot jp wrote:

> Date: 11 Jun 2004 00:36:43 -0000
> From: gotom at debian dot or dot jp
>     <sourceware-bugzilla@sources.redhat.com>
> To: folkert@vanheusden.com
> Subject: [Bug regex/215] memoryleak in regexec
>
>
> ------- Additional Comments From gotom at debian dot or dot jp  2004-06-11 00:36 -------
> Please send small test case.
>
> --
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |WAITING
>
>
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=215
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>



Folkert van Heusden

+--------------------------------------------------------------------------+
| UNIX sysop? Then give MultiTail ( http://www.vanheusden.com/multitail/ ) |
| a try, it brings monitoring logfiles to a different level! See:          |
| http://www.vanheusden.com/multitail/features.html for a feature list.    |
+---------------------------------------------------= www.vanheusden.com =-+



-- 


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

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



More information about the Glibc-bugs mailing list