User and Reference Guide

  • 2020
  • 10/23/2020
  • Public Content

Loading the Intel® Debug Extensions for WinDbg* for Intel® Processor Trace

When installed correctly, WinDbg* detects the extension automatically. If WinDbg* does not detect and load the extension automatically or if the extension was installed manually, perform one of the following actions:
  • Place
    in a directory where WinDbg* searches for extensions by default. These are usually all directories in the
    environment variable and some others. To display all searched directories, use the
    command in WinDbg*.
  • Add the path to
    to the
    environment variable. Create that variable, if it doesn’t exist.
  • Use the
    command in WinDbg* to add the directory containing
    to the search path.
    This setting only applies to the current debug session and is not saved when WinDbg* is closed.
Usually, WinDbg* loads detected extensions automatically. If this fails, you can load the extension manually. Use the
.load ptext32
.load ptext64
command in WinDbg*, depending on whether you are using a 32-bit or 64-bit version of WinDbg*.
For more information on loading debug extensions in WinDbg*, see the WinDbg* help system.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804