public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/5028] New: segfault in regex engine when using C collation and multibyte chars
Date: Thu, 13 Sep 2007 15:01:00 -0000	[thread overview]
Message-ID: <20070913150121.5028.aurelien@aurel32.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

glibc's regular expression engine crashes with segmentation fault whenever 
trying to compile a regular expression with non-ASCII range expressions if
LC_CTYPE is a UTF-8 locale but LC_COLLATE is set to C or POSIX. This
is a common setup among users who want traditional codepoint-order
sorting but need UTF-8 encoding.

$ LANG=en_US.UTF-8 LC_COLLATE=C grep '[Á-ä]'
Segmentation fault

This is also reproducible with a simple C program.

-- 
           Summary: segfault in regex engine when using C collation and
                    multibyte chars
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
        AssignedTo: drepper at redhat dot com
        ReportedBy: aurelien at aurel32 dot net
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=5028

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-09-13 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 15:01 aurelien at aurel32 dot net [this message]
2007-09-13 15:02 ` [Bug regex/5028] " aurelien at aurel32 dot net
2007-09-24  3:32 ` 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=20070913150121.5028.aurelien@aurel32.net \
    --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).