[Bug libstdc++/63614] With gcc-4.8.3 and -stdgnu++0x call to std::this_thread::get_id() creates SIGSEV

2014-11-04 Thread dyle at dyle dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63614 Oliver Maurhart dyle at dyle dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug libstdc++/63614] New: With gcc-4.8.3 and -stdgnu++0x call to std::this_thread::get_id() creates SIGSEV

2014-10-22 Thread dyle at dyle dot org
Severity: critical Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: dyle at dyle dot org Things have worked recently until I run into a SIGSEV rigtht in the guts of std::this_thread::id(). I tried several compiler options but still

[Bug libstdc++/63614] With gcc-4.8.3 and -stdgnu++0x call to std::this_thread::get_id() creates SIGSEV

2014-10-22 Thread dyle at dyle dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63614 dyle at dyle dot org changed: What|Removed |Added Severity|critical|minor --- Comment #1 from dyle

[Bug libstdc++/63614] With gcc-4.8.3 and -stdgnu++0x call to std::this_thread::get_id() creates SIGSEV

2014-10-22 Thread dyle at dyle dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63614 --- Comment #3 from dyle at dyle dot org --- (In reply to Jonathan Wakely from comment #2) (In reply to dyle from comment #0) Is this a gcc bug? Is it possible that std::this_thread::get_id() SIGSEVs? Yes it's possible if you don't use