Alex Sokolek
Member
Hi. I need some clarification and/or help with a multi-threaded application being debugged with Visual Studio.
I notice that when I hit a breakpoint in a thread, it stops, and I can examine the status and values, but when I step to the next instruction, the debugger goes back to the original breakpoint. I think I understand that a different thread is hitting the breakpoint, and that when one thread is stopped, they all seem to stop, until I go forward. Is this understanding correct?
Is there a way to hold the other threads, while I single step the first one? Also, is there anything in the debugger that will identify the particular thread that is stopped at the breakpoint? If it matters, I have Visual Studio 2022 Community, Version 17.9.6, and I am debugging a C++ program. Thanks.
I notice that when I hit a breakpoint in a thread, it stops, and I can examine the status and values, but when I step to the next instruction, the debugger goes back to the original breakpoint. I think I understand that a different thread is hitting the breakpoint, and that when one thread is stopped, they all seem to stop, until I go forward. Is this understanding correct?
Is there a way to hold the other threads, while I single step the first one? Also, is there anything in the debugger that will identify the particular thread that is stopped at the breakpoint? If it matters, I have Visual Studio 2022 Community, Version 17.9.6, and I am debugging a C++ program. Thanks.
Last edited:
