public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/5718] Uninitialised struct member in re_compile_internal causes crash in regfree
Date: Mon, 04 Feb 2008 13:56:00 -0000 [thread overview]
Message-ID: <20080204135554.19354.qmail@sourceware.org> (raw)
In-Reply-To: <20080204132153.5718.rrt@sc3d.org>
------- Additional Comments From bonzini at gnu dot org 2008-02-04 13:55 -------
Can you please pick an old copy of regex (one with the texinfo manual in it)
from ftp.gnu.org and check how translate is documented? Given the way it works
now, I would say that it does need to malloced memory (unless you do the extra
effort to NULL the field out before calling regfree).
My personal theory is that in olden times free(3) was enough to free a GNU
regex. Now it's not anymore and you're forced to call regfree.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5718
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2008-02-04 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 13:22 [Bug regex/5718] New: " rrt at sc3d dot org
2008-02-04 13:37 ` [Bug regex/5718] " rrt at sc3d dot org
2008-02-04 13:56 ` bonzini at gnu dot org [this message]
2008-02-04 14:04 ` rrt at sc3d dot org
2008-02-04 14:11 ` jakub at redhat dot com
[not found] <bug-5718-132@http.sourceware.org/bugzilla/>
2014-07-02 7:43 ` 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=20080204135554.19354.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@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: 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).