public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "folkert at vanheusden dot com" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug regex/215] New: memoryleak in regexec Date: Thu, 10 Jun 2004 21:21:00 -0000 [thread overview] Message-ID: <20040610212104.215.folkert@vanheusden.com> (raw) 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.
next reply other threads:[~2004-06-10 21:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-10 21:21 folkert at vanheusden dot com [this message] 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
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=20040610212104.215.folkert@vanheusden.com \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@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: linkBe 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).