Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

224 lines
8.3 KiB

  1. Microsoft(R) Debugging Tools for Windows(R)
  2. Version 6.0 Release Notes
  3. June 2002
  4. -----------------------------------------------------------------------------
  5. Contents
  6. Overview
  7. What's New
  8. Known Issues
  9. Programs
  10. Debugger Extensions
  11. Software Development Samples
  12. Documentation
  13. Redistributables
  14. More Information
  15. Feedback
  16. -----------------------------------------------------------------------------
  17. Overview
  18. Debugging Tools for Windows(R) contains tools to analyze and debug OS and
  19. application failures.
  20. The kernel debugger is KD.exe. It can be installed and run on Windows LE and
  21. Windows Server 2003. It can debug all the platforms listed below.
  22. The user-mode debugger is CDB.exe. It can be installed and used on Windows LE
  23. and Windows Server 2003. It can be used to debug 32-bit X86
  24. applications as well as native 64-bit applications.
  25. WinDbg.exe is the GUI version of the debugger. It supports both user-mode
  26. and kernel-mode debugging. It can be installed and run on Windows LE and
  27. Windows Server 2003. It can debug all the platforms listed below.
  28. Supported platforms:
  29. Windows NT 4.0 (x86)
  30. Windows 2000 (x86)
  31. Windows XP (All CPU architectures)
  32. Windows Server 2003 (All CPU architectures)
  33. -----------------------------------------------------------------------------
  34. What's New
  35. This release of Debugging Tools for Windows contains many bug fixes and new
  36. enhancements. The debuggers are stable and more reliable than previous releases
  37. and we recommend that you upgrade to this version.
  38. It is also a requirement to use this latest version if you wish to do kernel
  39. debugging of Windows Server 2003. Older versions (including 3.0.20.0) will
  40. not work with the latest Windows Server 2003 build.
  41. Here's a list of some of the changes in WinDbg 6.0:
  42. * Numerous improvements to !analyze
  43. * Don't lock PDB files when opened by the debugger (use SHARE_FILE_DELETE)
  44. * New symchk.exe utility which can be used to download symbols from
  45. the symbol server prior to a debugging session
  46. * New SYMOPT_SECURE debugger option to secure the host machine when remote
  47. debugging is enabled
  48. * New stepping commands pc and tc, and new tracing options with wt
  49. * Multiple dump files can now be loaded in the same debug session
  50. simultaneously
  51. * Many new search options added to the 's' command
  52. * Many new options for user mode minidump file creation
  53. * Better Ctrl-C support for long symbol operations
  54. * Allow lmv to show resource strings of kernel drivers
  55. * Other new and improved commands include
  56. .writemem, bm, kl, knf, .symfix+, .reload -w, !exchain, .closehandle,
  57. !apc, !analyze -f, .process -r, .thread -r, .cls, .logopen /t,
  58. .remote_exit, .enable_long_status, !slist, !evlog
  59. * Improved documentation
  60. * And lots of bug fixes, including:
  61. * Fixes for numerous Windows XP debugger extension issues
  62. * Fixes for various WinDbg crashes that people have reported using the
  63. Windows Error Reporting feature in Windows XP.
  64. -----------------------------------------------------------------------------
  65. Known Issues
  66. None.
  67. Other issues:
  68. -------------
  69. If you need to find source that was compiled at a different location than
  70. the current location to the source, use the ".srcpath" command.
  71. -----------------------------------------------------------------------------
  72. Programs
  73. This distribution includes the following debuggers:
  74. KD - Command-line kernel debugger
  75. NTSD - Command-line user-mode debugger
  76. CDB - Command-line user-mode debugger (variant of NTSD)
  77. WinDbg - GUI kernel debugger
  78. The Helpful Tools option is installed by default and includes these
  79. debugger-related tools:
  80. gflags - Global Flags Editor
  81. breakin - Utility to force a breakin in another process being debugged
  82. remote - Remote Command Line
  83. kill - Task Killing Utility
  84. list - File List Utility
  85. logviewer - Display API logs created with the .logext extension from
  86. the debugger
  87. symchk - utility to check validity of symbol files, or download symbols
  88. from a symbol server prior to a debugging session
  89. symstore - Creates a symbol server for automatic symbol lookup
  90. tlist - Task List Viewer
  91. umdh - Heap Analysis Tool
  92. The following tools have been incorporated into KD.exe and WinDbg.exe. They
  93. are also provided with Helpful Tools as small stubs that point you to use the
  94. debugger.
  95. dumpchk - Dump Checking Utility
  96. dumpexam - Dump Examining Utility
  97. -----------------------------------------------------------------------------
  98. Debugger Extensions
  99. Debugger Extensions are DLLs which WinDbg, CDB, NTSD, and KD can use to provide
  100. additional debugger commands. The Windows XP debugger extensions are in the
  101. winxp subdirectory and include:
  102. exts.dll
  103. kdexts.dll
  104. The debugger has awareness of these subdirectories, and will not be able
  105. to find them if these subdirectories are renamed or moved.
  106. If a custom extension DLL is to be used, it should be placed in its own
  107. directory. The user can then set the debugger extension path variable so the
  108. debugger can find the extension. Debugger extension can also be loaded in
  109. the debugger using fully qualified path names.
  110. For Windows XP, Ntsdexts.dll ships with the operating system, in
  111. %systemroot%\system64, and is not included in this distribution.
  112. All of the debuggers search for debugger extension DLLs in the
  113. following places:
  114. %NT_DEBUGGER_EXTENSION_PATH%;
  115. %DIRECTORY_FROM_WHICH_KDNTSD_IS_LAUNCHED%\WINEXT;
  116. %DIRECTORY_FROM_WHICH_KDNTSD_IS_LAUNCHED%\%TARGET_PLATFORM%;
  117. %DIRECTORY_FROM_WHICH_KDNTSD_IS_LAUNCHED%;
  118. %Path%
  119. where TARGET_PLATFORM is winxp.
  120. Use the "version" command in KD/NTSD to see what the extension search
  121. path, and to note where extension DLLs are loaded from.
  122. *** The NT 4 and Win2K debugger extensions were NOT ported and recompiled for
  123. 64 bit. In order to use the NT4 and Win2K extensions, the 32 bit Debugging
  124. Tools package should be installed.
  125. -----------------------------------------------------------------------------
  126. Software Development Samples
  127. Header files, libs and samples for debugger extensions are provided in this
  128. package. They are not installed by default. The "SDK" component of the package
  129. must be selected during the install to get the samples installed.
  130. The samples will compile by using the latest Windows XP DDK or SDK.
  131. The header files and libs in this package should replace any existing version
  132. of the header files or libs that are shipped with the DDK or SDK.
  133. Using the samples and headers with the Windows 2000 SDK or DDK will cause
  134. compilation errors.
  135. -----------------------------------------------------------------------------
  136. Documentation
  137. For documentation on how to use these debuggers and related tools, see the
  138. help file debugger.chm that is included with the tools. This documentation
  139. has been improved and expanded since the last release.
  140. -----------------------------------------------------------------------------
  141. Redistributables
  142. Please read the license agreement during setup for legal information regarding
  143. redistributable files. If this is a retail release, the license agreement
  144. mentions that redist.txt gives a list of the files that are redistributable.
  145. -----------------------------------------------------------------------------
  146. More Information
  147. For more information on debugging, see the Debugging Tools for Windows
  148. web page, <http://www.microsoft.com/ddk/debugging/>.
  149. We encourage people to get the new debugger off the web "often", as
  150. we do many updates.
  151. -----------------------------------------------------------------------------
  152. Feedback
  153. We are interested in your feedback on the tools. Please mail suggestions or
  154. bug reports to [email protected]. This is not a support alias, but your
  155. feedback will help us to plan future changes for these tools and will make
  156. them more useful to you in the future.
  157. -----------------------------------------------------------------------------