I'm using VS 2k8 SP1 (on Win2k8 x64 server), and I notice that a breakpoint with a condition set can produce quite flaky behavior, depending on how deep in the call stack the conditioned-breakpoint is found.
So if I place it on a routine deep in my code, the program execution breaks at the right time (I can tell because of console outpu), but the IDE no longer knows which thread is the one that hit the breakpoint, and acts like it doesn't know why or where it stopped.
I can do one of two things to fix the problem. Either I remove the condition altogether, leaving a vanilla breakpoint or I take that same breakpoint, with the same condition, and place it "higher" in my code (higher in relation to the call stack...closer to 'main' for example).
This strikes me as very strange behavior. Any explanation or suggested fix?