Rediger

Del via

Tools included in Debugging Tools for Windows

  • Artikkel

Debugging Tools for Windows includes several tools in addition to the debugging engine and debugging environments. The tools are in the installation directory of Debugging Tools for Windows.

Tools and utilities

Name Description
Breakin Causes a user-mode break to occur in a process. For help, open a Command Prompt window, go to the installation directory, and enter breakin /?.
DumpChk Validate a memory dump file.
GFlags Control registry keys and other settings.
Kill Terminate a process.
List (File List Utility) For help, open a Command Prompt window, go to the installation directory, and enter list /?.
Logger and LogViewer Record and display function calls and other actions of a program.
PLMDebug Use the Windows debugger to debug Windows app that run under Process Lifecycle Management (PLM). With PLMDebug, you can take manual control of suspending, resuming, and terminating a Windows app.
TList List all running processes.
UMDH Analyze heap allocations.
USBView Display USB host controllers and connected devices.
USBView2 Display USB host controllers and connected devices. For help, open a Command Prompt window, go to the installation directory, and enter USBView2 /?.

Symbol and source tools

Name Description
AgeStore Remove old entries in the downstream store of a symbol server or a source server.
DBH Display information about the contents of a symbol file.
PDBCopy Remove private symbol information from a symbol file, and control that public symbols are included in the file.
SrcSrv A source server that can be used to deliver source files while debugging.
SymChk Compare executable files to symbol files to verify that the correct symbols are available.
SymProxy Create a single HTTP symbol server on your network that all your debuggers can point to. This approach has the benefit of pointing to multiple symbol servers (both internal and external) with a single symbol path, handling all authentication, and increasing performance via symbol caching. Symproxy.dll is in the SymProxy folder in the installation directory.
SymSrv A symbol server that the debugger can use to connect to a symbol store. For information about working with the symbol server, see Microsoft public symbols.
SymStore Create a symbol store. See Using SymStore.

Remote and proxy debugger tools

Name Description
DbgRpc Display Microsoft Remote Procedure Call (RPC) state information. See RPC debugging and Using the DbgRpc tool.
DbgSrv A process server used for remote debugging. See Process servers (user mode).
DbEngPrx A repeater (small proxy server) used for remote debugging. See Repeaters.
KDbgCtrl (Kernel Debugging Control) Control and configure the kernel debugging connection. See Using KDbgCtrl.
KdSrv A KD connection server used for remote debugging. See KD connection servers (kernel mode).
RTList (Remote Task List Viewer) List running processes via a DbgSrv process server. For help, open a Command Prompt window, go to the installation directory, and enter rtlist /?.
Remote Remotely control any console program, including KD, CDB, and NTSD. See Remote debugging by using Remote.exe.

Installation directory

The default installation directory for 64-bit OS installations of the debugging tools is C:\Program Files (x86)\Windows Kits\10\Debuggers\. If you have a 32-bit OS, you can find the Windows Kits folder under C:\Program Files. To determine whether you should use the 32-bit or 64-bit tools, see Choosing the 32-bit or 64-bit debugging tools.

Tools related to Debugging Tools for Windows