Using windbg debug ASL and DTM fail

Windbg debug ASL

Windbg uses the host and target methods for debugging. This is a common system-level debugging method. It uses the host machine to debug the target machine. Therefore, two machines are generally required ..
1. Connect the two machines first. There are three connection methods.
Com
Ieee1394: This is quite common in Nb, and basically does not exist on the server. Therefore, if your Nb has a 1394 Interface, you can use 1394usb2. 0 debug cable, which must be a special type of cable, which is not sold in China. It seems that there is only one type of foreign product, and the debug port of EHCI is used to output the debug information. So what should I do if you don't have all three? There will always be a pcimca interface on your Nb, so that your boss will be bleeding to buy a pcimca to switch to a COM port.

2. Set the target machine to debug it in two steps.
2.1 set the OS to be In the debug mode. For more information, see http://msdn.microsoft.com/enus/library/ms791518.aspx. you can use the msconfig Program , Set boot. ini-> advance-> debug option.
2.2 replace ACPI on the target machine. sys File, download your corresponding OS checked build (that is, the debug version), such as XP or Server 2003, which is now publicly available, namely XP and Server 2003, other operating systems can be obtained only after msdn registration. For example, if my operating system is Server 2003 SP1, go to the Microsoft website to find the checked build version. Download the version, decompress it, and go to the i386 directory to find ACPI. sy _, this file is compressed. Use expand to decompress it: Expand ACPI. sy _ ACPI. sys, boot the target machine to safe mode, and search for ACPI in drive C. sys, rename or delete all the items that can be found, and extract the ACPI from the checked build. sys replaces the target system
Restart the file c: \ windows \ system32 \ drivers \ ACPI. sys ~~~ This section can refer to the http://blog.csdn.net/EFIBIOS/archive/2007/03/12/1526763.aspx
3. Set host machine
3.1 install windbg. Find it by yourself.
3.2 configure symbols. debug symbols is the address of various program functions and variables on the target machine. To debug the target system, symbols is indispensable. In
Http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx here for the symbols corresponding to the target system, note that the symbols version must be with your targe above the ACPI. the version of sys is the same. Otherwise, the debugger cannot find ACPI. sys and the ACPI Debugger in, checked build must use
The symbol file of the checked build .. Set the symbols installation path in windbg .. Under the File menu .. You can find it .. Run windbg-> kernel debug, select com or 1394, and restart target. When targetos is started, you can see the windbg connection information and target OS information, debug ACPI, you can press Ctrl + break to stop the target when the OS runs the scroll bar, and then DEBUG
4 .! AMLI
5 .! AMLI Debugger: Open ACPI debugger. If no response is returned, it indicates that the operation is successful. If there is an error message, re-check the settings.
6 .! AMLI set traceon
! AMLI set verboseon
! AMLI set spewon
Turn on the global debugging output. After this is enabled, all the ASL code from the operating system run will be output, so it will be very slow. If you do not debug the code here, set this before debugging .. You can use these options to trace how ACPI runs on the OS. If you want to debug an ACPI method, you can use it! Amli bp method_path, such! Amlibp \ _ sb. pci0.pe01. _ ADR, then the OS will break when running this method, and then you can use P for a single step to check the execution status. In the ASL code of bios, you can use the following method to output What You Want To windbg:
1. Output a value, such as store (local0, debug)
2. Output a string, such as store ("start trace ASL with windbg", debug)

Read the full text

Category:ACPI view comments