Analyze Dump Files by Using Platform Builder (Compact 7)

3/12/2014

When you analyze a dump file by using Platform Builder, Platform Builder creates a dynamic association between the dump file and the kernel debugger. (For information about the kernel debugger, see Kernel Debugger.) Platform Builder displays data, such as the call stack, from the dump file in the standard debugging windows.

To obtain the most information from a dump file, a debugger needs access to the executable files (EXE and DLL), symbol files (PDB), and the source code of the OS and applications that were running on the device at the time of the dump file capture. The EXE, DLL, and PDB files are created during the OS build process and are typically saved on the development computer in the flat release directory of the associated OS design. However, you may have archived these files elsewhere after you built the OS. In the following procedure, you specify the path to these files on your development computer.

To analyze a dump file by using Platform Builder

1. Copy the dump file, *.kdmp, from the device to your development computer.

2. On your development computer, in Windows Explorer, double-click the dump file. Platform Builder starts and creates a new solution. The dump file is a project of the solution.

3. In Platform Builder, click Debug, and then click Symbol Search Path.

4. In the Symbol Search Path dialog box, type the path of the executable files (EXE and DLL) and symbol files (PDB) of the OS and applications that were running on the device at the time of the dump file capture. If you enter multiple paths, separate them with semicolons.

5. Click OK.

6. In Platform Builder, on the Device menu, click (auto) Dump1. If you cannot see the Device menu, click View, click Toolbars, and then click Target.

7. On the Target menu, click Attach Device to start debugging the dump file.

   The kernel debugger starts in break mode at the source code line that generated the exception. A dialog box appears that notifies you of the exception, the same as it would if you were debugging the device directly. If the debugger can find the source code on your development computer, the source file appears in a source window with a yellow arrow pointing to the source code line that generated the exception.

8. Click OK to close the dialog box that displays the exception.

9. Click Debug, click Windows, and then click one of the following debugging windows:

   • Call Stack Window
   • Threads Window
   • Modules Window
   • Processes Window
   • Disassembly Window
   • Registers Window
   • Variables Window
     You access the Variables window by clicking Autos.

Analyze the data in these windows as you typically would if you were debugging the device directly.

See Also

Concepts

Analyze Dump Files