Often WinDbg will enter a state where it is *Busy* performing an operation.
Often this is due to some mistake I made trying to dt some_variable_itll_never_find or setting a break point somewhere without symbols or the 1000's of other mistakes I make fumbling around this tool.
Is there a way to cancel the current operation?
You can exit WinDbg by choosing Exit from the File menu or by pressing ALT+F4.
In WinDbg, use Debug | Break or press CTRL+BREAK. In kernel-mode debugging, you can cancel commands from the keyboard of the target computer by pressing CTRL+C. You can use the . cls (Clear Screen) command to clear all of the text from the Debugger Command window.
I don't have the tool now, but as far as I remember it should be Ctrl+Break.
Sometimes Ctrl+Break doesnt work. At that point you may use Debug menu -> Break.
Thanks
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With