That may be key board specific...At work I have a ctrl + pause key on my laptop that stops execution. I just bought the PC I'm posting on and it doesn't have a pause key. I wonder what key replaced it?
There's a button on the VS toolbar while debugging that with the tooltip "Break All (Ctrl+Alt+Break)". You can click that or use that key combo in VS to break all threads. Not sure why you didn't see that yourself - it even uses the pause icon, to go along with the play and stop icons.
I believe that Ctrl+Break in the application will just break the main thread, although I'm not 100% sure about that. Easy to test though. Of course, there's generally only one thread executing your code anyway, but may not always be.
Last edited by jmcilhinney; Jul 21st, 2021 at 11:41 PM.
That may be key board specific...At work I have a ctrl + pause key on my laptop that stops execution. I just bought the PC I'm posting on and it doesn't have a pause key. I wonder what key replaced it?
I have Pause on my keyboard too. They were probably concerned that gamers rage-quitting would press the Break key and expect their keyboard to explode.
I tried the Control + Break and got the following results (see attached).
The Control + Break did not work.
Do I have to load something else to get it to work?
Without being able to see all of the text it is hard to say exactly what is the issue. I suspect that it has in fact entered break mode but it was either executing code that wasn't compiled as debug code and can't load the symbols or possible it was inside of "other code" such as the framework, API call, or 3rd party library that doesn't have any debug symbols.
Does the call stack window show anything useful such as the current module name or a call stack that could show what code of yours invoked this code?
So, why are you looking at this? There are a few things that might cause you to want to try to study something without a breakpoint, and that is now appearing relevant. There must be something going on where you felt that either you couldn't set a breakpoint, or that it wouldn't do, so what is happening that you are trying to investigate?
Was any code actually being executed at the time? If this is a WinForms application that was waiting for user input then what exactly are you expecting to happen?