public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "max at cert dot cx" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/61582] C++11 regex memory corruption Date: Tue, 01 Jul 2014 18:54:00 -0000 [thread overview] Message-ID: <bug-61582-4-Hf9bCa5JaJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61582-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #12 from Maksymilian Arciemowicz <max at cert dot cx> --- Ups. Check this (.*{100}{300}) gcc version 4.10.0 20140701 (experimental) (GCC) -------- Starting program: /home/cx/REtrunk/kozak5/t3 '(.*{100}{300})' Program received signal SIGSEGV, Segmentation fault. 0x000000000040c22a in std::__detail::_Executor<char const*, std::allocator<std::sub_match<char const*> >, std::regex_traits<char>, true>::_M_dfs(std::__detail::_Executor<char const*, std::allocator<std::sub_match<char const*> >, std::regex_traits<char>, true>::_Match_mode, long) () --------
next prev parent reply other threads:[~2014-07-01 18:54 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-23 0:05 [Bug libstdc++/61582] New: C11 " max at cert dot cx 2014-06-23 8:13 ` [Bug libstdc++/61582] " redi at gcc dot gnu.org 2014-06-25 9:54 ` [Bug libstdc++/61582] C++11 " redi at gcc dot gnu.org 2014-06-25 18:01 ` redi at gcc dot gnu.org 2014-06-25 19:15 ` max at cert dot cx 2014-06-25 23:31 ` max at cert dot cx 2014-06-26 7:11 ` max at cert dot cx 2014-06-26 7:17 ` timshen at gcc dot gnu.org 2014-06-26 7:59 ` max at cert dot cx 2014-07-01 3:06 ` timshen at gcc dot gnu.org 2014-07-01 18:54 ` max at cert dot cx [this message] 2014-07-04 10:25 ` max at cert dot cx 2014-07-04 18:00 ` timshen at gcc dot gnu.org 2015-08-14 17:00 ` timshen at gcc dot gnu.org 2015-08-14 17:01 ` timshen at gcc dot gnu.org 2021-05-04 12:32 ` rguenth at gcc dot gnu.org 2021-12-15 23:57 ` redi at gcc dot gnu.org 2021-12-16 23:40 ` 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-61582-4-Hf9bCa5JaJ@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).