[Bug libstdc++/61582] C++11 regex memory corruption

2021-12-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Jonathan Wakely changed: What|Removed |Added Last reconfirmed|2014-06-25 00:00:00 |2021-12-16 Assignee|timshen

[Bug libstdc++/61582] C++11 regex memory corruption

2021-12-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #23 from Jonathan Wakely --- (In reply to M Welinder from comment #22) > FWIW, there is an excellent overview of regular expression engine pitfalls > and methods here: > > https://swtch.com/~rsc/regexp/regexp1.html >

[Bug libstdc++/61582] C++11 regex memory corruption

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

[Bug libstdc++/61582] C++11 regex memory corruption

2019-02-21 Thread terra at gnome dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 M Welinder changed: What|Removed |Added CC||terra at gnome dot org --- Comment #22

[Bug libstdc++/61582] C++11 regex memory corruption

2017-02-10 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #21 from Tim Shen --- (In reply to Pádraig Brady from comment #20) > Any status update on this. GCC7 is looming... > Thanks. Unfortunately I haven't get a chance to work on this. I plan to put up a one-line tweak on the internal

[Bug libstdc++/61582] C++11 regex memory corruption

2017-02-10 Thread P at draigBrady dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Pádraig Brady changed: What|Removed |Added CC||P at draigBrady dot com --- Comment #20

[Bug libstdc++/61582] C++11 regex memory corruption

2016-03-30 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Tim Shen changed: What|Removed |Added CC||chaoskeeper at mail dot ru --- Comment #19

[Bug libstdc++/61582] C++11 regex memory corruption

2016-03-25 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Tim Shen changed: What|Removed |Added CC||bisqwit at iki dot fi --- Comment #18 from

[Bug libstdc++/61582] C++11 regex memory corruption

2015-12-03 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Tim Shen changed: What|Removed |Added CC||kerukuro at gmail dot com --- Comment #17

[Bug libstdc++/61582] C++11 regex memory corruption

2015-08-14 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Tim Shen timshen at gcc dot gnu.org changed: What|Removed |Added CC||morandidodo at

[Bug libstdc++/61582] C++11 regex memory corruption

2015-08-14 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Tim Shen timshen at gcc dot gnu.org changed: What|Removed |Added CC||antialize at gmail

[Bug libstdc++/61582] C++11 regex memory corruption

2014-07-04 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #13 from Maksymilian Arciemowicz max at cert dot cx --- @Tim: do you need help?

[Bug libstdc++/61582] C++11 regex memory corruption

2014-07-04 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #14 from Tim Shen timshen at gcc dot gnu.org --- (In reply to Maksymilian Arciemowicz from comment #13) @Tim: do you need help? This is what I'm going to do: https://gcc.gnu.org/ml/libstdc++/2014-07/msg8.html Please send to

[Bug libstdc++/61582] C++11 regex memory corruption

2014-07-01 Thread max at cert dot cx
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

[Bug libstdc++/61582] C++11 regex memory corruption

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

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-26 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #7 from Tim Shen timshen at gcc dot gnu.org --- (.*{100}{100}{100}) seems to be a stack overflow. It's because regex executor uses recursion. It could be fixed (not segfault but memory exhaustion) by using a std::stack and simulate

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-26 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #8 from Maksymilian Arciemowicz max at cert dot cx --- (In reply to Tim Shen from comment #7) (.*{100}{100}{100}) seems to be a stack overflow. It's because regex executor uses recursion. It could be fixed (not segfault but memory

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-26 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #9 from Tim Shen timshen at gcc dot gnu.org --- (In reply to Maksymilian Arciemowicz from comment #8) (In reply to Tim Shen from comment #7) (.*{100}{100}{100}) seems to be a stack overflow. It's because regex executor uses

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-26 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #10 from Maksymilian Arciemowicz max at cert dot cx --- There is also one other alternative like this http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/regex/regcomp.c.diff?r1=1.29r2=1.30f=h

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|RESOLVED|NEW Last

[Bug libstdc++/61582] C++11 regex memory corruption

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

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-25 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #5 from Maksymilian Arciemowicz max at cert dot cx --- Thanks for feedback. I'm going verify this on trunk

[Bug libstdc++/61582] C++11 regex memory corruption

2014-06-25 Thread max at cert dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61582 --- Comment #6 from Maksymilian Arciemowicz max at cert dot cx --- @Jonathan: true but check this case cx@cx:~/REtrunk/kozak5$ ~/gccTRUNK/bin/g++ -v Using built-in specs. COLLECT_GCC=/home/cx/gccTRUNK/bin/g++