### Limitations During Postmortem Debugging

Once you have started debugging a dump file, you can use a subset of debugger features to examine registers, storage (if available), and code for the executable that caused the trap. You can access only the following debugger monitors:

- Registers monitor
- Storage monitor
- Call Stack monitor
- Local Variables monitor

You cannot change the contents of items in these monitors (for example, registers in the registers monitor). Where the core file does not contain appropriate information, question marks or messages such as "expression evaluation failed" may appear in place of data. For example, if stack information was not saved, local variable values may not be displayed, even though the names of those variables are.

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

- Run and stop commands
- Step commands
- Commands to set, clear, disable, enable, or delete breakpoints.