Interactive output doesn't currently play nice with threads. It appears as if a second cin.operator<< is never reached because another thread also uses cin and hence blocks the first. Possible solutions: use boost.asio, or otherwise wrap the cin (which has its own locks) usage.
Interactive output doesn't currently play nice with threads. It appears as if a second cin.operator<< is never reached because another thread also uses cin and hence blocks the first. Possible solutions: use boost.asio, or otherwise wrap the cin (which has its own locks) usage.