Or, optionally (provided that Visual Studio is not installed), take a copy of Windows Debugging Tools , install and run the application from the debugger (windbg.exe), or bind it to an already running application:
windbg [.exe] -pn program.exe
or
windbg [.exe] -p process_id
A break in the debugger at the point you want to monitor the stack trace (Ctrl + Break). Switch to the thread of interest (most likely, the main thread of execution):
~ 0s
Fix characters for system modules (and possibly for the application, if available):
* Fix characters for the application
.sympath path_to_app_symbols
* configure where the debugger will load and store system characters
.symfix + path_where_system_symbols_will_be_stored
* force the debugger to reload characters
<i> .reload
Issue a call stack command:
<i> kb
source share