public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "kevin.braunsdorf at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/13396] New: culry is treated as a range in cases where POSIX says it should not be Date: Wed, 09 Nov 2011 18:54:00 -0000 [thread overview] Message-ID: <bug-13396-132@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13396 Bug #: 13396 Summary: culry is treated as a range in cases where POSIX says it should not be Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: drepper.fsp@gmail.com ReportedBy: kevin.braunsdorf@gmail.com Classification: Unclassified Target: Red Hat Enterprise Linux Server release 5.4 (Tikanga) Created attachment 6046 --> http://sourceware.org/bugzilla/attachment.cgi?id=6046 C program to repeat the bug In the RE "^[$](S|{SHELL}|k|K)$" the curly braced are not range specifiers. Other versions of regcomp accept this RE with no errors (egrep, *BSD's implmentation and others), but the later glibc complains: regcomp: ^[$](S|{SHELL}|k|K)$: Invalid preceding regular expression (I include a test program for it.) -- 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 reply other threads:[~2011-11-09 18:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-09 18:54 kevin.braunsdorf at gmail dot com [this message] 2011-11-09 18:56 ` [Bug regex/13396] curly " kevin.braunsdorf at gmail dot com 2011-11-09 22:14 ` bonzini at gnu dot org 2011-11-10 4:44 ` bugdal at aerifal dot cx 2011-11-10 6:39 ` bonzini at gnu dot org 2014-06-27 11:37 ` 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=bug-13396-132@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).