Is there a way to make multi-threaded debugging in visual studio work the same way as eclipse?

In eclipse, you stop at a breakpoint and all other threads continue to run. If they stop at a breakpoint, they stop, but your context remains the thread you were working with at the time. If you hit f8 (run), it can switch your context to a different thread that is already stopped at the breakpoint, but if you do f5 (step forward) or f6 (go), you will always stay on the same thread.

In visual studio (I'm new to visual studio) I find that if I step over (f10) or take a step (f11) I can (and probably will) switch my context to another thread and replay my progress if I won't manually go back to the original theme.

I understand that I can freeze all other threads, but it becomes cumbersome if I want to switch threads sometimes. This should be an option somewhere, but visual studio is very full of options and I haven't found one yet.

+3


source to share


1 answer


http://screencast.com/t/itxo6Job

This is the only option I can think of that might help, but according to the MSDN blog ( http://ppe.blogs.msdn.com/b/zainnab/archive/2010/10/22/break-all-processes- when-one-process-breaks-vstipdebug0029.aspx ), it might not get you where you want it.



This somewhat related question might also help: "Step over" when debugging multi-threaded programs in Visual Studio

+2


source







All Articles