public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "galens at capaccess dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58576] New: std::regex_match() reports mismatched braces on a valid regex
Date: Mon, 30 Sep 2013 03:06:00 -0000	[thread overview]
Message-ID: <bug-58576-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58576

            Bug ID: 58576
           Summary: std::regex_match() reports mismatched braces on a
                    valid regex
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: galens at capaccess dot org

Created attachment 30929
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30929&action=edit
Archive containing the g++ -v -save-temps compile log, the generated .ii file
and the original .cpp with the minimum-to-reproduce test case.

I attempted to use a regex to validate qualified hostnames.

However, when I used the regex from this thread (
http://stackoverflow.com/questions/1418423/the-hostname-regex ), with or
without replacing the [0-9A-Za-z] with [:alnum:] (and properly escaping the
backslashes), I get a regex_error exception thrown on std::regex_match() call,
with a regex_constants::error_brack as the reported code().


Using: An unmodified copy of gcc 4.8.1 20130603 from the Fedora 19 primary
repository (rpm ver: 4.8.1-1.fc19 )

(I use 4-spaces-per-tab in my source code, which isn't relevant for the code,
but might make hand-tracing of Parens, Braces, and Brackets I did in comments
more understandable.) 

(And, yes, I know replacing [0-9A-Za-z] with [:alnum:] isn't a legitimate
change WRT domain name validity, unless I force a 'C' locale.  It was just
easier to read when hunting down this issue.)


             reply	other threads:[~2013-09-30  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30  3:06 galens at capaccess dot org [this message]
2013-09-30  3:14 ` [Bug libstdc++/58576] " galens at capaccess dot org
2013-09-30  7:40 ` schwab@linux-m68k.org
2013-09-30  9:46 ` redi at gcc dot gnu.org
2013-10-01 15:26 ` timshen at gcc dot gnu.org

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-58576-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).