Microsoft’s WinDbg* is a kernel debugger which can debug certain processes via standard network, serial cable, USB, etc. If system integrators are stuck at a faulty software driver, the only solution to identify this bug is a JTAG-based connection, which basically halts the entire system. So Intel added a JTAG plug-in with an additional Intel® Processor Trace (Intel® PT) viewer to support the Windows* startup phase. This video will give you an introduction of that and show how to establish a connection to start using Intel Debug Extensions for WinDbg.
00m :27s - Introduction
00m : 54s - Usage Scenario and Limitations
01m : 35s - Set Up
01m : 55s - Launching Intel® Debug Extensions for WinDbg* and Establishing connection
03m : 07s - Running WinDbg* Session
03m : 58s - Snapshot of the WinDbg GUI for debugging
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