public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/1357] memory leak in re_compile_pattern()
Date: Mon, 14 Oct 2013 14:18:00 -0000 [thread overview]
Message-ID: <bug-1357-132-l0WRM5FOEw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-1357-132@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=1357
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |---
--- Comment #4 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
I'm not sure what "will does not compile" means. If you change "/Optional" to
"//Optional" then the code given here compiles with -D_GNU_SOURCE. Maybe
there's something wrong with the code, but you need a clearer analysis if so
before closing the bug (and WONTFIX should only apply e.g. to a bug in a port
that's been removed; INVALID is what to do if the fault is in the user program
or the requested change is otherwise undesirable, just leave the bug open if
you're not interested in fixing it).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-14 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1357-132@http.sourceware.org/bugzilla/>
2013-10-12 17:13 ` neleai at seznam dot cz
2013-10-14 14:18 ` jsm28 at gcc dot gnu.org [this message]
2005-09-19 21:24 [Bug regex/1357] New: " root at liwave dot com
2005-10-14 5:49 ` [Bug regex/1357] " drepper at redhat dot com
2005-12-30 20:52 ` drepper at redhat dot com
2006-05-02 21:56 ` drepper 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-1357-132-l0WRM5FOEw@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).