[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2021-09-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 Jonathan Wakely changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread shaoqin2 at illinois dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #11 from Bobby Lu --- (In reply to Tim Shen from comment #9) > I see. Can you show the ulimit *stack* information? I believe it's -s. > > Also, try -O2 so that the functions are inlined. > > As for the stack overflow, it's a known i

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #10 from Jonathan Wakely --- Are you sure it's an infinite loop? It looks like a null pointer dereference: 0x00403f64 in std::_Any_data::_M_access (this=0x0)

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #9 from Tim Shen --- I see. Can you show the ulimit *stack* information? I believe it's -s. Also, try -O2 so that the functions are inlined. As for the stack overflow, it's a known issue. To workaround this, please set a bigger stac

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread shaoqin2 at illinois dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 Bobby Lu changed: What|Removed |Added Attachment #43661|0 |1 is obsolete|

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread shaoqin2 at illinois dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #7 from Bobby Lu --- Created attachment 43661 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43661&action=edit Gdb stack trace. $ ulimit unlimited

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #6 from Tim Shen --- Will you able to provide a stack trace and/or ulimit information?

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread timshen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 Tim Shen changed: What|Removed |Added CC||timshen at gcc dot gnu.org --- Comment #5 fro

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread shaoqin2 at illinois dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 Bobby Lu changed: What|Removed |Added Attachment #43659|0 |1 is obsolete|

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread shaoqin2 at illinois dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #3 from Bobby Lu --- Created attachment 43659 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43659&action=edit Single source file to reproduce the bug compile with g++ -std=c++11 regex.cpp -lpthread ./a.out Segmentation fault

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug libstdc++/84865] Regular expression regex_search falls into infinite loop causing segfault on crayxc machines

2018-03-14 Thread shaoqin2 at illinois dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84865 --- Comment #1 from Bobby Lu --- No compiler warning is generated