Unusual debugger behavior
Restriction:
This does not apply when debugging interpreted Java programs.
If the debugger behaves in unexpected ways when you are
debugging core files, it is usually an indication that the core file is missing necessary
information, or that modules cannot be located.
There are limitations during postmortem debugging regarding what subset of debugging
features and actions is normally available for core files. Missing core file information
and missing modules can further limit the debugger in the following ways:
- The contents of local variables cannot be displayed or used in expression evaluation.
This indicates that the program stack is absent from the core file.
- No entries appear in the Call Stack monitor. This also indicates that the program stack
is absent from the core file. If some entries appear in the Call Stack monitor but others
are missing, this indicates that the process call stack has an entry for a
function
contained within a module that is not available. This situation causes the call stack to
be truncated in the monitor; that is, only the entries in the stack up to that entry are
shown.
- Threads are missing. This indicates that the current execution location of a thread is
contained in a module that is not available. The debugger handles this situation as if the
thread never existed.
- You cannot use a variable of static storage duration in an expression (for example, in
the Monitor Expression dialog). This indicates that data segments are missing from
the core file.
- Memory in the storage window shows "??????" instead of the expected contents.
This indicates that the core file was missing those memory locations (for the stack, data
segments, and memory-mapped regions), or that the debugger could not locate necessary
modules (for code segment regions).

Limitations during postmortem debugging