public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "rrt at sc3d dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/5718] New: Uninitialised struct member in re_compile_internal causes crash in regfree Date: Mon, 04 Feb 2008 13:22:00 -0000 [thread overview] Message-ID: <20080204132153.5718.rrt@sc3d.org> (raw) regfree frees preg->translate (regcomp.c:629), but if the GNU API was used to initialise the pattern buffer, then translate has not been initialised, so may well contain a bogus value. Fix is to initialise it to NULL in re_compile_internal (say, just after regcomp.c:724), and best workaround I can think of is to make sure that you zero the re_pattern_buffer when allocating it. -- Summary: Uninitialised struct member in re_compile_internal causes crash in regfree Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: drepper at redhat dot com ReportedBy: rrt at sc3d dot org CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com 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 reply other threads:[~2008-02-04 13:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-04 13:22 rrt at sc3d dot org [this message] 2008-02-04 13:37 ` [Bug regex/5718] " rrt at sc3d dot org 2008-02-04 13:56 ` bonzini at gnu dot org 2008-02-04 14:04 ` rrt at sc3d dot org 2008-02-04 14:11 ` jakub 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=20080204132153.5718.rrt@sc3d.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: 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).