If Windows stops working and displays a blue screen, the computer has shut down abruptly to protect itself from data loss and displays a bug check code. For more information about creating and using symbol files, see Symbols for Windows debugging. Symbol files store a variety of data that are not required when running the executable binaries, but symbol files are very useful when debugging code. For more information, see Debugging Using CDB and NTSD. CDB and NTSDĪlso available are the Microsoft Console Debugger (CDB) and Microsoft NT Symbolic Debugger (NTSD). For more information, see Debugging Using KD and NTKD. KD and NTKD are identical in every way, except that NTKD spawns a new text window when it is started, whereas KD inherits the Command Prompt window from which it was invoked. There are four command line debuggers that are available for specialized environments and for those that prefer a command line interface. The Windows debuggers support the following versions of Windows for both the host and target computers. In either case, the computer that is running the debugger is called the host computer, and the computer that is being debugged is called the target computer. Sometimes the debugger and the code being debugged run on the same computer, but other times the debugger and the code being debugged run on separate computers. The Windows debuggers can run on x86-based, 圆4-based, or Arm-based processors, and they can debug code that is running on those same architectures. For debugging managed code, such as C#, using the Visual Studio debugger is often the easiest way to get started. For information on debugging in Visual Studio, see Debugging in Visual Studio. Visual Studio includes its own debugging environment and debugging engine, which together are called the Visual Studio debugger. This debugging engine is also called the Windows debugger, and the six debugging environments are collectively called the Windows debuggers. For descriptions of these environments, see Debugging Environments.Īll of these debugging environments provide user interfaces for the same underlying debugging engine, which is implemented in the Windows Symbolic Debugger Engine (Dbgeng.dll). If your computer has Visual Studio and the WDK installed, then you have six available debugging environments. To download the installer or an ISO image, see Windows SDK on Windows Dev Center.
#Script debugger install
You can install the Debugging Tools for Windows alone, without the Windows SDK or WDK, by starting installation of the Windows SDK and then selecting only Debugging Tools for Windows in the list of features to install (and clearing the selection of all other features).
#Script debugger driver
To get the WDK, see Download the Windows Driver Kit (WDK).ĭebugging Tools for Windows is included in the Windows Software Development Kit (SDK).
You can get Debugging Tools for Windows as part of a development kit or as a standalone tool set:ĭebugging Tools for Windows is included in the Windows Driver Kit (WDK).
#Script debugger how to
For a full list of the tools, see Tools Included in Debugging Tools for Windows.įor directions on how to download and install the just the Windows debugger, see Download and install the WinDbg Windows debugger. In addition to the debuggers such as WinDbg, Debugging Tools for Windows includes a set of tools that are useful for debugging.
0 kommentar(er)
