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-31
Set Execute Memory-Access Breakpoint
Set Execute Memory-Access Breakpoint
The BM command can set an execute memory-access breakpoint. An execute
memory-access breakpoint causes Debug to execute a specified string of Debug
commands when the breakpoint location itself is accessed in the specified manner.
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 BM command is:
address
is the address where the breakpoint is to occur. For more information, see Address
Syntax on page 3-12.
indicates the type of memory access that triggers the breakpoint. Valid options
depend on the type of processor you are using, as noted in this list:
command-string
is a string of Debug commands separated by semicolons (;) that is saved when
you enter the breakpoint and is executed when the breakpoint is executed. The
string of Debug commands is not examined for syntax errors until it is executed.
ALL
For more information on this option, see Set Unconditional Memory-Access Breakpoint
on page 4-24.
Considerations
•
For more information on setting an unconditional memory-access breakpoint, see
Considerations on page 4-25.
•
Change access is not allowed with execute memory-access breakpoint.
BM address , access
{, ( command-string ) [, ALL ] }
{ [ , ALL ] ( command-string ) }
R Break on a read access
RW Break on a read/write access
WR Break on a read/write access; equivalent to RW
W Break on a write access