-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breakpoint and Step Over with multithreading #515
Comments
@pub-pub in |
thanks a lot, @karthiknadig but i had to hardcode and one more thing: maybe there's also a parameter that keeps me Stepping Over inside my thread without pausing all other threads? |
@pub-pub debugpy has lot more control over this, but I am not sure if there is a stop only current option yet. This might be a feature request on debugpy. You can ask for it here https://github.com/microsoft/debugpy |
Even though it has the yellow line it should work. |
there's an issue with debugging python code that utilizes multithreading.
i set a breakpoint, start debugging, execution pauses as expected, but when i press 'Step Over' (F10) debugger does not go to the next expression (line) in the current thread, but jumps to some random locations in other running threads, and i have to 'Step Over' again and again until i return to my current thread.
'Step Over' feature must be limited the current (paused) thread.
the same issue was reported for Visual Studio a couple of years ago https://developercommunity.visualstudio.com/t/make-the-debugger-stick-to-the-current-thread-inst/351390
The text was updated successfully, but these errors were encountered: