Debug Manual

Debug Commands
Debug Manual—421921-003
4-8
Set Unconditional Code Breakpoint
ALL
indicates that the breakpoint applies to all processes in the processor executing
the code being debugged. The ALL option is allowed only in privileged mode. A
global breakpoint (this is, a breakpoint set with the ALL option) is delivered to any
process that executes the code location that is breakpointed. A private breakpoint
(without the ALL option) is delivered only to the process that created the
breakpoint.
Considerations
•
When you set a breakpoint, Debug displays information describing this breakpoint.
For more information on 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.
•
A global breakpoint is associated with a particular memory object, regardless of
any process. The breakpoint persists as long as the containing memory object
exists; the breakpoint disappears when the memory object is deleted. By contrast,
a private breakpoint is associated with a particular memory object within a
particular process; the breakpoint disappears when the object disappears or the
process terminates.
°
A global breakpoint in system code, or in a system library, persists until the
processor is reloaded.
°
A global breakpoint in a public SRL or public DLL persists as long as that SRL
or DLL persists. The breakpoint disappears if the SRL is untitled or the
processor is reloaded.
°
A global breakpoint in user code, a user library, private SRL, or private DLL
persists as long as at least one process is executing that code, library, SRL, or
DLL. The breakpoint disappears when no process is executing that code,
library, SRL, or DLL.
°
A global breakpoint in an OSS shared memory object persists as long as the
object persists.