|
WinDbg is a multipurpose debugger for the Microsoft Windows computer operating system, distributed on the Worldwide Web by Microsoft.〔https://msdn.microsoft.com/en-us/windows/hardware/hh852365.aspx〕 Debugging is the process of finding and resolving errors in a system; in computing it also includes exploring the internal operation of software as a help to development. It can be used to debug user mode applications, device drivers, and the operating system itself in kernel mode. Like the better-known Visual Studio Debugger it has a graphical user interface (GUI), but is more powerful and has little else in common. WinDbg can be used for debugging kernel-mode memory dumps, created after what is commonly called the Blue Screen of Death which occurs when a bug check is issued.〔http://www.techrepublic.com/blog/windows-and-office/how-do-i-use-windbg-debugger-to-troubleshoot-a-blue-screen-of-death/〕 It can also be used to debug user-mode crash dumps. This is known as post-mortem debugging.〔https://delog.wordpress.com/2010/09/10/post-mortem-debugging-of-net-applications-using-windbg/〕 WinDbg can automatically load debugging symbol files (e.g., PDB files) from a server by matching various criteria (e.g., timestamp, CRC, single or multiprocessor version) via SymSrv (SymSrv.dll),〔https://support.microsoft.com/en-us/kb/311503/〕 instead of the more time-consuming task of creating a symbol tree for a debugging target environment. If a private symbol server is configured, the symbols can be correlated with the source code for the binary. This eases the burden of debugging problems that have various versions of binaries installed on the debugging target by eliminating the need for finding and installing specific symbols version on the debug host. Microsoft has a public symbol server that has most of the public symbols for Windows 2000 and later versions of Windows (including service packs).〔https://msdn.microsoft.com/en-us/library/windows/hardware/ff552208(v=vs.85).aspx〕 Recent versions of WinDbg have been and are being distributed as part of the free Debugging Tools for Windows suite, which shares a common debugging back-end between WinDbg and command line debugger front-ends like KD, CDB, and NTSD. Most commands can be used as is with all the included debugger front-ends. ==Extensions== WinDbg allows the loading of extension DLLs〔https://msdn.microsoft.com/en-us/library/windows/hardware/ff563964(v=vs.85).aspx〕 that can augment the debugger's supported commands and allow for help in debugging specific scenarios: for example, displaying an MSXML document given an IXMLDOMDocument, or debugging the Common Language Runtime (CLR).〔https://msdn.microsoft.com/en-us/magazine/cc163791.aspx〕 These extensions are a large part of what makes WinDbg such a powerful debugger. WinDbg is used by the Microsoft Windows product team to build Windows, and everything needed to debug Windows is included in these extension DLLs. Extension commands are always prefixed with !. While some extensions are used only inside Microsoft, most of them are part of the public Debugging Tools for Windows package. The extension model is documented in the help file included with the Debugging Tools for Windows. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「WinDbg」の詳細全文を読む スポンサード リンク
|