Breakpoint actions

This topic explains CodeWarrior enhancements to standard breakpoint behavior. While the standard behavior of breakpoints of a debugger is to stop execution at a specific spot, you can use breakpoint actions to extend the breakpoint behavior and define other actions that occur when program execution reaches the breakpoint.

Breakpoint actions let you:

specify specific tasks to perform,
manage a list of actions, where each action has specific properties,
attach specific actions to individual breakpoints,
control the order in which the breakpoint actions occur, and
execute the Debugger Shell commands.

You can associate more than one action with a breakpoint. The debugger executes the associated breakpoint actions when the program execution encounters the breakpoint. The following table lists and describes breakpoint actions.

Table 1. Breakpoint actions
Action	Description
Debugger Shell Action	Executes Debugger Shell commands or a Debugger Shell script.
Sound Action	Plays the specified sound.
Log Action	Logs messages to a console. The messages can be literal strings or the result of an expression that the debugger evaluates.
Resume Action	Halt the program execution for a specified time and then resumes the program execution.
External Tool Action	Invokes a program, which is external to the debugger.