Debug Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- Execution Modes on TNS/R Systems
- What User Access Is Required for Debugging
- How to Make a Process Enter Debug
- How to Select Debug as the Debugger
- Why a Process Enters Debug
- How to Determine Process State on a Trap or Signal
- Ending a Debug Session
- What Appears in the Debug Header Message
- How to Use Debug
- How Debug Breakpoints Work
- 2 Using Debug on TNS/R Processors
- 3 Debug Command Overview
- 4 Debug Commands
- Command Summary
- A Command
- AMAP Command
- B Command
- BASE Command
- BM Command
- C Command
- CM Command
- D Command
- DJ Command
- DN Command
- EX[IT] Command
- F[ILES] Command
- FC Command
- FN Command
- FNL Command
- FREEZE Command
- HALT Command
- H[ELP] Command
- I Command
- IH Command (TNS/R Native and OSS Processes)
- INSPECT Command
- LMAP Command
- M Command
- MH Command (TNS/R Native and OSS Processes)
- P[AUSE] Command
- PMAP Command (Accelerated Programs)
- PRV Command
- R Command
- S[TOP] Command
- T Command
- V Command
- VQ Command
- VQA Command
- = Command
- ? Command
- A Error Messages
- B ASCII Character Set
- C Command Syntax Summary
- Register Syntax
- Expression Syntax
- Address Syntax
- A Command
- AMAP Command
- B Command
- BASE Command
- BM Command
- C Command
- CM Command
- D Command
- DJ Command
- DN Command
- EX[IT] Command
- F[ILES] Command
- FC Command
- FN Command
- FNL Command
- FREEZE Command
- HALT Command
- H[ELP] Command
- I Command
- IH Command
- INSPECT Command
- LMAP Command
- M Command
- MH Command
- Output-Device Syntax
- P[AUSE] Command
- PMAP Command
- PRV Command
- R Command
- S[TOP] Command
- T Command
- V Command
- VQ Command
- VQA Command
- = Command
- ? Command
- D Session Boundaries
- E Correspondence Between Debug and Inspect Commands
- F Sample Debug Sessions
- Glossary
- Index

Debug Commands
Debug Manual—421921-003
4-15
Set Execute Code Breakpoint
•
When you set a breakpoint, Debug displays information describing this breakpoint.
For a description of the information displayed, see Display Breakpoints on
page 4-16.
•
When debugging accelerated programs, you can set breakpoints in TNS code only
on instructions that are register-exact points or memory-exact points.These points
are marked in displays by the I and PMAP commands. For more information, see
Section 2, Using Debug on TNS/R Processors.
Examples
106,01,00012-B 4+52, 5?10
106,01,00012-B UC.2, 423, 3?10
106,01,00012-B UL.1, 5+23, 40?3
248,01,00012-B N 0X70451210, 0x2323 ? 0x100
Example of Setting a Trace Code Breakpoint
The address where the breakpoint is located is determined in the same manner as
previously described in Set Unconditional Code Breakpoint on page 4-7. For more
information on an example of setting a trace code breakpoint, see Appendix F, Sample
Debug Sessions.
Set Execute Code Breakpoint
The B command can set an execute code breakpoint. An execute code breakpoint
causes Debug to execute a specified string of Debug commands when the breakpoint
location itself is executed.
After executing the specified command string, Debug prompts for additional Debug
commands, unless the specified command string contains an R (resume) command.
The execute form of the B command is:
address
is the code address where the breakpoint is to be placed. For more information,
see Address Syntax on page 3-12. The address mode must follow the same
guidelines as those stated earlier in this section for specifying the code address
when setting an unconditional code breakpoint.
command-string
is a string of Debug commands separated by semicolons (;) that is saved when
you enter the breakpoint and executed when the breakpoint is executed. The
string of Debug commands is not examined for syntax errors until it is executed.
B address {, ( command-string ) [, ALL ] }
{ [, ALL], ( command-string ) }