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.

265 lines
9.7 KiB

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