[Bug libstdc++/50703] std::stringstream not thread-safe

2011-10-17 Thread hoenle2...@kayser-threde.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50703 --- Comment #7 from hoenle2...@kayser-threde.com 2011-10-17 08:17:21 UTC --- @Jonathan: You ask "was gcc built with a non-default value for --enable-clocale ?". I don't think so. We perform cross development on Windows with MinGW a

[Bug libstdc++/50703] std::stringstream not thread-safe

2011-10-13 Thread hoenle2...@kayser-threde.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50703 --- Comment #3 from hoenle2...@kayser-threde.com 2011-10-13 07:56:47 UTC --- I will try libstdc++ 4.6.x or 4.5.x. Question: May I use this new library with the relatively old compiler I am currently utilizing or do I need to upgrade to a newer

[Bug libstdc++/50703] std::stringstream not thread-safe

2011-10-12 Thread hoenle2...@kayser-threde.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50703 --- Comment #1 from hoenle2...@kayser-threde.com 2011-10-12 15:36:50 UTC --- Created attachment 25475 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25475 debugger screenshot

[Bug libstdc++/50703] New: std::stringstream not thread-safe

2011-10-12 Thread hoenle2...@kayser-threde.com
Component: libstdc++ AssignedTo: unassig...@gcc.gnu.org ReportedBy: hoenle2...@kayser-threde.com Our multi-threaded software (running on the SPARC compatible LEON3 processor for space applications under the RTEMS 4.9.4 operating system) always locks up at the same location