public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "antialize at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/67212] New: Infinite recurtion in std::regex_match Date: Fri, 14 Aug 2015 08:17:00 -0000 [thread overview] Message-ID: <bug-67212-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67212 Bug ID: 67212 Summary: Infinite recurtion in std::regex_match Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: antialize at gmail dot com Target Milestone: --- Created attachment 36184 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36184&action=edit Crashing program The following code, crashes for some instances of line (as given in the attachment): std::regex lineExp("tpie::update_fractions\\([ ]*\"([^\"]+)\"[ ]*,[ ]*([^, ]+)[ ]*,[ ]*([^\\) ]+)[ ]*\\);.*", std::regex::extended); std::string line = <some_long_string_here> std::smatch matches; std::regex_match(line, matches, lineExp); The crash ocure as we are running out of stack space in some possible infinite recurtion. The context of the code can be seen here https://github.com/thomasmoelhave/tpie/blob/cpp11-cleanup/tpie/fractional_progress.cpp#L64 The issue is triggered by: g++ -std=c++11 test2.cc && ./a.out
next reply other threads:[~2015-08-14 8:17 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-14 8:17 antialize at gmail dot com [this message] 2015-08-14 17:01 ` [Bug libstdc++/67212] " timshen at gcc dot gnu.org 2015-08-14 17:54 ` 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-67212-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: 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).