v19.0.0.12 64-bit on Ubuntu 14.04 x64
I am debugging a multi-threaded process via debug-executable. I notice that sometimes when that process breaks into the debugger (an ASSERT for instance) that the current thread is set to thread 0 instead of the thread that hit the breakpoint. So the callstack is wrong and I have to go hunt through the thread window until I can find the right thread.
I'm not sure if this is a new problem or not, but it's quite annoying.
-John
