弄清楚为什么 WinDBG 处于 "BUSY" 状态?

Figure out why WinDBG is in "BUSY" state?

我无法弄清楚为什么 WinDBG 处于忙碌状态:

有没有办法找到描述?

无法找到 WinDbg 忙碌的确切原因,但您可以使用“.lastevent”验证它响应的最后一个事件。但是,对于您的特定情况,它正忙于寻找 kernel32!CreateFileW 的符号和源代码。如果您为事件注册了扩展程序,您将收到更改符号状态

IDebugEventCallbacksWide::ChangeSymbolState

DEBUG_CSS_LOADS The engine has loaded some module symbols.
DEBUG_CSS_UNLOADS   The engine has unloaded some module symbols.
DEBUG_CSS_SCOPE The current symbol scope has changed.
DEBUG_CSS_PATHS The executable image, source , or symbol search paths have changed.
DEBUG_CSS_SYMBOL_OPTIONS    The symbol options have changed.
DEBUG_CSS_TYPE_OPTIONS  The type options have changed.

同时检查这个:

IDebugEventCallbacksWide::ChangeEngineState

这些事件是:

DEBUG_CES_CURRENT_THREAD    The current thread has changed, which implies that the current target and current process might also have changed.
DEBUG_CES_EFFECTIVE_PROCESSOR   The effective processor has changed.
DEBUG_CES_BREAKPOINTS   One or more breakpoints have changed.
DEBUG_CES_CODE_LEVEL    The code interpretation level has changed.
DEBUG_CES_EXECUTION_STATUS  The execution status has changed.
DEBUG_CES_ENGINE_OPTIONS    The engine options have changed.
DEBUG_CES_LOG_FILE  The log file has been opened or closed.
DEBUG_CES_RADIX The default radix has changed.
DEBUG_CES_EVENT_FILTERS The event filters have changed.
DEBUG_CES_PROCESS_OPTIONS   The process options for the current process have changed.
DEBUG_CES_EXTENSIONS    Extension DLLs have been loaded or unloaded. (For more information, see Loading Debugger Extension DLLs.)
DEBUG_CES_SYSTEMS   A target has been added or removed.
DEBUG_CES_ASSEMBLY_OPTIONS  The assemble options have changed.
DEBUG_CES_EXPRESSION_SYNTAX The default expression syntax has changed.
DEBUG_CES_TEXT_REPLACEMENTS Text replacements have changed.