audk/SourceLevelDebugPkg at a72526804846e44773174a7b4800168e889d831a - audk

History

pgao2 0a16169be8 Fix the issue that might prevent single step in PeCoffExtraActionLib (right after triggering breakpoint to notify image load/unload) work. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@10870 6f19259b-4bc3-4df7-8a09-765794883524		2010-09-13 02:42:14 +00:00
..
Include	Import SourceLevelDebugPkg.	2010-09-12 06:43:36 +00:00
Library	Fix the issue that might prevent single step in PeCoffExtraActionLib (right after triggering breakpoint to notify image load/unload) work.	2010-09-13 02:42:14 +00:00
Readme.txt	minor format update to make text wrap around column 80	2010-09-13 02:03:04 +00:00
SourceLevelDebugPkg.dec	…
SourceLevelDebugPkg.dsc	…

Readme.txt

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using 
Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled
with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit 
Debugger Tool (Intel(R) UDK Debugger Tool).

The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:
http://www.intel.com/technology/efi. 

NOTE: In addition to the known issues listed in the user manual, the following 
anomalies have been observed:

1) When using a USB debug cable, after the TARGET completes a reset during memory
   initialization, the connection between the HOST and the TARGET may be lost 
   (e.g. WinDbg reports busy status and does not respond to a break request). A 
   work around for this issue is to unplug the USB debug cable and then plug the
   cable back in. A new debug session may then be started.

Readme.txt Unescape Escape

Readme.txt