### Debug Dump Files

You can debug dump files created by the ITRAPPER utility in much the same way as you debug live executables. However, because a dump file is not executable, any debugger commands to do with running, stepping, or setting breakpoints will not work when you are debugging a dump file.

To start debugging a dump file, from the command shell type:

idebug [path]dumpfilename

where dumpfilename is the name of the dump file you want to debug. You can also enter the dump file name from the Startup dialog, by starting the debugger without parameters, or by choosing File->Startup from the Source or Session Control windows.

Once you have started debugging a dump file, you can use a subset of debugger features to examine registers, storage, and code for the executable that caused the trap. You can access all the debugger monitors (registers, call stack, storage, local variables, program, private and popup), but you cannot change the contents of items in these monitors (for example, registers in the registers monitor).

The following debugger commands are disabled, and icons for them are hidden or greyed out, when you are debugging a dump file:

- Halt command
- Step commands
- Commands to set, clear, disable, enable, or delete breakpoints.

The Run command is available, but its only effect is to cause a redisplay of the exception that caused the trap.

Obtain a Dump File