[Bug libstdc++/61601] C++11 regex resource exhaustion

2021-05-04 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org,

[Bug libstdc++/61601] C++11 regex resource exhaustion

2021-05-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug libstdc++/61601] C++11 regex resource exhaustion

2019-10-25 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #10 from Tim Shen --- (In reply to Eric Gallager from comment #9) > (In reply to Tim Shen from comment #7) > > (In reply to Maksymilian Arciemowicz from comment #6) > > > > Do you have any other testcases? > > > > > > for trunk? mayb

[Bug libstdc++/61601] C++11 regex resource exhaustion

2019-10-02 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #9 from Eric Gallager --- (In reply to Tim Shen from comment #7) > (In reply to Maksymilian Arciemowicz from comment #6) > > > Do you have any other testcases? > > > > for trunk? maybe you have to use ::regex_match > > std::regex_ma

[Bug libstdc++/61601] C++11 regex resource exhaustion

2015-02-02 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #8 from Maksymilian Arciemowicz --- > there's no memory problem, it just takes exponentially long time to run > (which is expected when using backtracking). call it cpu resource exhaustion (CWE-400) > > To avoid it, you can use Tho

[Bug libstdc++/61601] C++11 regex resource exhaustion

2015-02-01 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #7 from Tim Shen --- (In reply to Maksymilian Arciemowicz from comment #6) > > Do you have any other testcases? > > for trunk? maybe you have to use ::regex_match std::regex_match("findme", std::regex("(.*{100}{200}findme)")); ther

[Bug libstdc++/61601] C++11 regex resource exhaustion

2015-02-01 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #6 from Maksymilian Arciemowicz --- > Do you have any other testcases? for trunk? maybe you have to use ::regex_match

[Bug libstdc++/61601] C++11 regex resource exhaustion

2015-02-01 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #5 from Tim Shen --- > cpu exhaustion not eliminated > > PoC: (.*{100}{200}findme) I tried to run: #include using namespace std; int main (int argc, char *argv[]) { string input; regex r(argv[1]); return 0; } Against '(.

[Bug libstdc++/61601] C++11 regex resource exhaustion

2014-07-01 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #4 from Maksymilian Arciemowicz --- cpu exhaustion not eliminated PoC: (.*{100}{200}findme)

[Bug libstdc++/61601] C++11 regex resource exhaustion

2014-06-30 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #3 from Tim Shen --- Author: timshen Date: Tue Jul 1 03:05:45 2014 New Revision: 212185 URL: https://gcc.gnu.org/viewcvs?rev=212185&root=gcc&view=rev Log: PR libstdc++/61061 PR libstdc++/61582 * include/bits/regex_automa

[Bug libstdc++/61601] C++11 regex resource exhaustion

2014-06-25 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 --- Comment #2 from Tim Shen --- (In reply to Jonathan Wakely from comment #1) > Tim, how hard would it be to hardcode limits somewhere for these cases? It's easy. 6 lines. I'll propose a patch soon.

[Bug libstdc++/61601] C++11 regex resource exhaustion

2014-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61601 Jonathan Wakely changed: What|Removed |Added CC||timshen at gcc dot gnu.org --- Comment