public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/17069] leak in regcomp Date: Thu, 19 Jun 2014 17:01:00 -0000 [thread overview] Message-ID: <bug-17069-132-NhhZAPsSRR@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 #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, master has been updated via 4d43ef1e7434d7d419afbcd754931cb0c794763c (commit) from 51a7380b8968251a49a4c5b0bc7ed1af5b0512c6 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=4d43ef1e7434d7d419afbcd754931cb0c794763c commit 4d43ef1e7434d7d419afbcd754931cb0c794763c Author: Andreas Schwab <schwab@linux-m68k.org> Date: Thu Jun 19 15:38:03 2014 +0200 Fix memory leak in regexp compiler (BZ #17069) ----------------------------------------------------------------------- Summary of changes: ChangeLog | 12 ++++++++++++ posix/Makefile | 12 +++++++++--- .../bench-timing-type.c => posix/bug-regex36.c | 12 +++++++----- posix/regcomp.c | 13 ++++++++++--- 4 files changed, 38 insertions(+), 11 deletions(-) copy benchtests/bench-timing-type.c => posix/bug-regex36.c (82%) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-19 17:01 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 [this message] 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 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-NhhZAPsSRR@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: 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).