public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "sbrabec at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/13637] incorrect match in multi-byte (non-UTF8) string Date: Mon, 27 Feb 2012 15:14:00 -0000 [thread overview] Message-ID: <bug-13637-132-2Nhe4x7scd@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13637-132@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13637 Stanislav Brabec <sbrabec at suse dot cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #6244|0 |1 is obsolete| | --- Comment #4 from Stanislav Brabec <sbrabec at suse dot cz> 2012-02-27 15:13:21 UTC --- Created attachment 6252 --> http://sourceware.org/bugzilla/attachment.cgi?id=6252 glibc-regex-incomplete-char.patch Updated patch. Changes since comment 3: - Testcase uses test-skeleton.c. - Uses SBC_MAX and includes "regex_internal.h". - Setup fastmap before call to re_compile_pattern. - bug-regex33.6 comment updated: There is one true and one false match. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-27 15:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-31 12:48 [Bug regex/13637] New: " leonardo at ngdn dot org 2012-02-10 19:22 ` [Bug regex/13637] " sbrabec at suse dot cz 2012-02-10 19:22 ` sbrabec at suse dot cz 2012-02-24 20:25 ` sbrabec at suse dot cz 2012-02-24 20:27 ` sbrabec at suse dot cz 2012-02-27 15:14 ` sbrabec at suse dot cz [this message] 2012-02-28 16:43 ` sbrabec at suse dot cz
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-13637-132-2Nhe4x7scd@http.sourceware.org/bugzilla/ \ --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).