From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-regex-return-614-listarch-glibc-bugs-regex=sources.redhat.com@sourceware.org>
Received: (qmail 11906 invoked by alias); 20 Jun 2014 04:08:44 -0000
Mailing-List: contact glibc-bugs-regex-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs-regex.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-regex-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs-regex@sourceware.org>
List-Help: <mailto:glibc-bugs-regex-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-regex-owner@sourceware.org
Received: (qmail 11864 invoked by uid 48); 20 Jun 2014 04:08:40 -0000
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:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: regex
X-Bugzilla-Version: 2.20
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: konstantin.s.serebryany at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 2.20
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-17069-132-kUv9UfOvMg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17069-132@http.sourceware.org/bugzilla/>
References: <bug-17069-132@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-06/txt/msg00018.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=17069

--- Comment #3 from Kostya Serebryany <konstantin.s.serebryany at gmail dot com> ---
Created attachment 7651
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7651&action=edit
larger pattern

The leak on original reproducer is gone, 
however on a larger pattern (attached) a very similar looking 
leak is still present:

Direct leak of 192 byte(s) in 6 object(s) allocated from:
    #0 0x494a39 in calloc
/home/kcc/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:95
    #1 0x7f3f2ed1c14b in parse_bracket_exp glibc-trunk/posix/regcomp.c:3052
    #2 0x7f3f2ed1c14b in parse_expression glibc-trunk/posix/regcomp.c:2265
    #3 0x7f3f2ed1d48f in parse_branch glibc-trunk/posix/regcomp.c:2193
    #4 0x7f3f2ed1d57d in parse_reg_exp glibc-trunk/posix/regcomp.c:2145
    #5 0x7f3f2ed1d9c8 in parse glibc-trunk/posix/regcomp.c:2114
    #6 0x7f3f2ed1d9c8 in re_compile_internal glibc-trunk/posix/regcomp.c:794
    #7 0x7f3f2ed1ec10 in __regcomp glibc-trunk/posix/regcomp.c:501
    #8 0x4b3338 in main (/home/kcc/tmp/a.out+0x4b3338)

-- 
You are receiving this mail because:
You are on the CC list for the bug.