How can I abort a long operation in WinDbg?

windows debugging windbg
Aardvark picture Aardvark · Oct 10, 2008 · Viewed 23.4k times · Source

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?

Answer

hakan picture hakan · Oct 10, 2008

I don't have the tool now, but as far as I remember it should be Ctrl+Break.

Related questions

What is your favourite Windbg tip/trick?

I have come to realize that Windbg is a very powerful debugger for the Windows platform & I learn something new about it once in a while. Can fellow Windbg users share some of their mad skills? ps: I am …

Read More
Kernel trace Windows 7 WinDbg

I'm getting no debug information when debugging en_windows_7_checked_build_dvd_x86_398742. I can't see even my own trace info (ATLTRACE). In opposite, Windows XP Checked works like a charm. I get "Bad QueryIdType:5" msg on debug session start …

Read More
when and how to use windbg kernel debugging

I found Windbg is very useful during development and debugging. but mostly i use windbg in use mode debugging. What kernel debugging can do in windbg? or When should I use windbg's kernel debugging? Is there a toturial about kernel …

Read More