public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/63990] New: regex_search increments a past-the-end iterator Date: Thu, 20 Nov 2014 09:49:00 -0000 [thread overview] Message-ID: <bug-63990-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63990 Bug ID: 63990 Summary: regex_search increments a past-the-end iterator Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: kariya_mitsuru at hotmail dot com Created attachment 34049 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34049&action=edit g++ -v The sample code below is aborted with "attempt to increment a past-the-end iterator". ========================================================================= #include <regex> #include <debug/string> int main() { __gnu_debug::string s = "a"; std::regex_search(s.begin(), s.end(), std::regex("b")); } ========================================================================= cf. http://melpon.org/wandbox/permlink/2EesivDageAWjAnN It seems that it always occurs if regex_search is not matched. It also seems that such an iterator is never accessed. cf. http://melpon.org/wandbox/permlink/PfGxfu5qjoqaDgEm I think that it may not cause any problem. But it is better to fix.
next reply other threads:[~2014-11-20 9:49 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 9:49 kariya_mitsuru at hotmail dot com [this message] 2014-11-21 3:48 ` [Bug libstdc++/63990] " timshen at gcc dot gnu.org 2023-07-20 11:35 ` redi 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-63990-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).