public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
* [Bug regex/215] New: memoryleak in regexec
@ 2004-06-10 21:21 folkert at vanheusden dot com
2004-06-11 0:36 ` [Bug regex/215] " gotom at debian dot or dot jp
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: folkert at vanheusden dot com @ 2004-06-10 21:21 UTC (permalink / raw)
To: glibc-bugs-regex
Hi,
I found a memoryleak in regexec.
I found it while running MultiTail (http://www.vanheusden.com/multitail) which
runs regexec quiet a few times.
Using valgrind I traced back the leakage in glibc:
==25067== 146920 bytes in 13997 blocks are still reachable in loss record 90 of
94
==25067== at 0x40027BAA: malloc (vg_replace_malloc.c:153)
==25067== by 0x40365649: re_node_set_init_copy (in /lib/libc-2.3.1.so)
==25067== by 0x40366764: create_cd_newstate (in /lib/libc-2.3.1.so)
==25067== by 0x403662E4: re_acquire_state_context (in /lib/libc-2.3.1.so)
==25067==
==25067==
==25067== 147728 bytes in 14167 blocks are still reachable in loss record 91 of
94
==25067== at 0x40027BAA: malloc (vg_replace_malloc.c:153)
==25067== by 0x40365649: re_node_set_init_copy (in /lib/libc-2.3.1.so)
==25067== by 0x40366384: create_newstate_common (in /lib/libc-2.3.1.so)
==25067== by 0x403665C3: create_cd_newstate (in /lib/libc-2.3.1.so)
==25067==
==25067==
==25067== 167724 bytes in 13977 blocks are still reachable in loss record 92 of
94
==25067== at 0x40027BAA: malloc (vg_replace_malloc.c:153)
==25067== by 0x4036674E: create_cd_newstate (in /lib/libc-2.3.1.so)
==25067== by 0x403662E4: re_acquire_state_context (in /lib/libc-2.3.1.so)
==25067== by 0x4035FF5C: check_matching (in /lib/libc-2.3.1.so)
==25067==
==25067==
==25067== 453344 bytes in 14167 blocks are still reachable in loss record 93 of
94
==25067== at 0x4002803A: calloc (vg_replace_malloc.c:284)
==25067== by 0x4036636A: create_newstate_common (in /lib/libc-2.3.1.so)
==25067== by 0x403665C3: create_cd_newstate (in /lib/libc-2.3.1.so)
==25067== by 0x403662E4: re_acquire_state_context (in /lib/libc-2.3.1.so)
if you need any more details, do not hesitate to contact me.
--
Summary: memoryleak in regexec
Product: glibc
Version: 2.3.2
Status: NEW
Severity: normal
Priority: P2
Component: regex
AssignedTo: gotom at debian dot or dot jp
ReportedBy: folkert at vanheusden 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=215
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug regex/215] memoryleak in regexec
2004-06-10 21:21 [Bug regex/215] New: memoryleak in regexec folkert at vanheusden dot com
@ 2004-06-11 0:36 ` gotom at debian dot or dot jp
2004-06-20 21:44 ` folkert at vanheusden dot com
2004-06-22 8:55 ` gotom at debian dot or dot jp
2 siblings, 0 replies; 4+ messages in thread
From: gotom at debian dot or dot jp @ 2004-06-11 0:36 UTC (permalink / raw)
To: glibc-bugs-regex
------- 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 are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug regex/215] memoryleak in regexec
2004-06-10 21:21 [Bug regex/215] New: memoryleak in regexec folkert at vanheusden dot com
2004-06-11 0:36 ` [Bug regex/215] " gotom at debian dot or dot jp
@ 2004-06-20 21:44 ` folkert at vanheusden dot com
2004-06-22 8:55 ` gotom at debian dot or dot jp
2 siblings, 0 replies; 4+ messages in thread
From: folkert at vanheusden dot com @ 2004-06-20 21:44 UTC (permalink / raw)
To: glibc-bugs-regex
------- 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug regex/215] memoryleak in regexec
2004-06-10 21:21 [Bug regex/215] New: memoryleak in regexec folkert at vanheusden dot com
2004-06-11 0:36 ` [Bug regex/215] " gotom at debian dot or dot jp
2004-06-20 21:44 ` folkert at vanheusden dot com
@ 2004-06-22 8:55 ` gotom at debian dot or dot jp
2 siblings, 0 replies; 4+ messages in thread
From: gotom at debian dot or dot jp @ 2004-06-22 8:55 UTC (permalink / raw)
To: glibc-bugs-regex
------- Additional Comments From gotom at debian dot or dot jp 2004-06-22 08:55 -------
2.3.1 is old version, please confirm your memory leak with the latest version.
If you find the problem with your glibc (ie: debian glibc), please submit bug
report to bugs.debian.org instead of bugzilla.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-06-22 8:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-06-10 21:21 [Bug regex/215] New: memoryleak in regexec folkert at vanheusden dot com
2004-06-11 0:36 ` [Bug regex/215] " gotom at debian dot or dot jp
2004-06-20 21:44 ` folkert at vanheusden dot com
2004-06-22 8:55 ` gotom at debian dot or dot jp
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).