On 3 October 2014 09:18, Henrik Mannerström wrote: > Do you have any suggestions on what to do next? Have you tried valgrind? Or compiling with GCC's -fstack-protector option? I can't reproduce the problem, and I think it's pretty unlikely std::string has that kind of bug without someone noticing years ago.
