Stepping in a multithreaded application

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765

[pub-pub]

i posted my initial issue here and it was successfully resolved.

now i'm using "steppingResumesAllThreads": false setting for debugging. but this solutions has a drawback, it pauses all other threads.

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

[Rich Chiodo (rchiodo)]

is it possible to add one more setting that will keep debugger Stepping inside my initial thread without pausing all other threads?

I may be confused as to what you're asking but this is what stepping does by default? If you hit F10, all threads run, a breakpoint is put on the next line in the current thread, and then the breakpoint hits. All threads pause again.

[pub-pub]

Are your threads all running the same code? That would explain why it would jump around. Unlike Visual Studio's C++ debugger, debugpy doesn't have a way to tie a breakpoint to just a specific thread.

no, my 'debugged' thread is different, it is some kind of 'watcher' thread, all other threads are workers and run the same code

[Rich Chiodo (rchiodo)]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

[pub-pub]

Hmm, then that sounds like a stepping issue. It shouldn't step into random code. It's supposed to step to the next line that's going to execute.

when i set "steppingResumesAllThreads": false it stays inside my 'debugged' thread, but when it's true it jumps outside

[Rich Chiodo (rchiodo)]

Well yeah because the other threads are paused, there's no new event for another line executing from any thread but the one you have paused.

When the next event comes in it should be checking if it's the step over/out location. And if it is, firing a breakpoint event. If the other thread isn't running the same code, then that location shouldn't be a possible step over/out location.

Do you have a sample app that reproduces the issue?

[pub-pub]

Do you have a sample app that reproduces the issue?

no, i'm working on the 'watcher' thread only,
but i will try to write smth short and see if i can reproduce the issue

[pub-pub]

sorry i don't know how to post source code here, so i attached it as txt file

on the screenshot you can see that my breakpoint is on line 12
now run the code and when it stops, press F10 five times and it will jump to line 7

when i was writing this sample i've noticed one strange thing.
when you uncomment line 6, the debugger will run fine and will not jump outside 'watcher' thread.

Untitled-1.txt

[Rich Chiodo (rchiodo)]

Thanks, I can reproduce the problem. Seems incorrect to me. I'm opening an issue.

[Rich Chiodo (rchiodo)]

#1765