public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "konstantin.s.serebryany at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/17069] leak in regcomp
Date: Fri, 20 Jun 2014 04:41:00 -0000 [thread overview]
Message-ID: <bug-17069-132-Z37k8aXaZD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17069-132@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17069
--- Comment #5 from Kostya Serebryany <konstantin.s.serebryany at gmail dot com> ---
Created attachment 7652
--> https://sourceware.org/bugzilla/attachment.cgi?id=7652&action=edit
build_charclass_op_leak.c
One more similarly looking leak, only differs in top frame: build_charclass_op
Direct leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x494a39 in calloc
/home/kcc/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:95
#1 0x7f8e3bed09da in build_charclass_op glibc-trunk/posix/regcomp.c:3598
#2 0x7f8e3bed1e9e in parse_expression glibc-trunk/posix/regcomp.c:2393
#3 0x7f8e3bed348f in parse_branch glibc-trunk/posix/regcomp.c:2193
#4 0x7f8e3bed357d in parse_reg_exp glibc-trunk/posix/regcomp.c:2145
#5 0x7f8e3bed39c8 in parse glibc-trunk/posix/regcomp.c:2114
#6 0x7f8e3bed39c8 in re_compile_internal glibc-trunk/posix/regcomp.c:794
#7 0x7f8e3bed4c10 in __regcomp glibc-trunk/posix/regcomp.c:501
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-20 4:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 5:53 [Bug regex/17069] New: " konstantin.s.serebryany at gmail dot com
2014-06-19 14:46 ` [Bug regex/17069] " fweimer at redhat dot com
2014-06-19 17:01 ` cvs-commit at gcc dot gnu.org
2014-06-19 20:35 ` schwab@linux-m68k.org
2014-06-20 4:08 ` konstantin.s.serebryany at gmail dot com
2014-06-20 4:09 ` konstantin.s.serebryany at gmail dot com
2014-06-20 4:41 ` konstantin.s.serebryany at gmail dot com [this message]
2014-06-20 12:04 ` cvs-commit at gcc dot gnu.org
2014-06-20 12:06 ` schwab@linux-m68k.org
2014-06-20 12:28 ` konstantin.s.serebryany at gmail dot com
2014-06-22 7:46 ` cvs-commit at gcc dot gnu.org
2014-08-28 10:26 ` cvs-commit at gcc dot gnu.org
2015-02-18 14:31 ` fweimer at redhat dot com
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=bug-17069-132-Z37k8aXaZD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@sourceware.org \
/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).