Debug Manual

Debug Commands
Debug Manual—421921-003
4-57
LMAP Command
•
If you invoke Debug from an Inspect process being used to debug multiple
processes, there is a possibility of both the Inspect process and Debug competing
to control the terminal. You might consider using either the Inspect or Debug pause
command to eliminate the contention.
•
If the Inspect debugger is used to set breakpoints on STOP or ABEND, the Inspect
debugger reports the event even if the event occurs when Debug is being used to
debug the process.
•
If PRV ON occurred earlier in Debug or SET PRIV MODE ON occurred earlier in
Inspect, you do not need to reissue PRV ON to Debug.
Example
This command switches from Debug to the Inspect debugger.
244,02,00033-INSPECT
INSPECT - Symbolic Debugger - ...
244,02,00033 MYPROG #MYPROC^MAIN.#29004(SMYPROG)
-MYPROG-
.
.
.
-MYPROG- SELECT DEBUGGER DEBUG ! Go back to Debug.
DEBUG P=%000236, E=%000207, UC.%00
244,02,00033-
LMAP Command
The LMAP command displays the name of the procedure, the offset from the base of
the procedure, and the code space, where a specified address lies. The form of the
LMAP command is:
address
is the address that is to be translated to a procedure name plus offset. For more
information, see Address Syntax on page 3-12.
Considerations
•
If you use the V command to vector to another process (V is a privileged
command), LMAP works only for global code areas (SC, SL, SCr, SLr); local code
addresses in the program of the target process are rejected.
•
The LMAP command displays nothing if the address is outside any procedure or if
no name is available.
•
The offset is displayed only if it is nonzero.
LMAP address