Anonymous

← Visual Studio

My feedback

  1. Make the debugger stick to the current thread instead of jumping around between threads!

    542 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    25 comments  ·  Visual Studio IDE » Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  AdminVisual Studio Team (Product Team, Microsoft Visual Studio) responded

    Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to address this suggestion in a future release. Thanks for capturing the pain points you feel when stepping through multithreaded applications while debugging. We will be providing an update soon.

    Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. If you have other breakpoints in your application and another thread hits one, then you will be debugging in the mixed thread state as described in this item.

    Kaycee Anderson
    Program Manager, Visual Studio

    Anonymous commented  · 

    If you want to see how to do it right, try out eclipse. They let you control the flow very easily.

Feedback and Knowledge Base

(thinking…)