Cancels a tracepoint. Format CANCEL TRACE [address-expression[, . . . ]]
1 – Parameters
address-expression Specifies a tracepoint to be canceled. Do not use the asterisk (*) wildcard character. Instead, use the /ALL qualifier. Do not specify an address expression when using any qualifiers except /EVENT, /PREDEFINED, or /USER.
2 – Qualifiers
2.1 /ACTIVATING
Cancels the effect of a previous SET TRACE/ACTIVATING command.
2.2 /ALL
By default, cancels all user-defined tracepoints. When used with /PREDEFINED, it cancels all predefined tracepoints but no user-defined tracepoints. To cancel all tracepoints, use /ALL/USER/PREDEFINED.
2.3 /BRANCH
Cancels the effect of a previous SET TRACE/BRANCH command.
2.4 /CALL
Cancels the effect of a previous SET TRACE/CALL command.
2.5 /EVENT
/EVENT=event-name Cancels the effect of a previous SET TRACE/EVENT=event-name command. Specify the event name (and address expression, if any) exactly as specified with the SET TRACE/EVENT command. To identify the current event facility and the associated event names, use the SHOW EVENT_FACILITY command.
2.6 /EXCEPTION
Cancels the effect of a previous SET TRACE/EXCEPTION command.
2.7 /INSTRUCTION
Cancels the effect of a previous SET TRACE/INSTRUCTION command.
2.8 /LINE
Cancels the effect of a previous SET TRACE/LINE command.
2.9 /PREDEFINED
Cancels a specified predefined tracepoint without affecting any user-defined tracepoints. When used with /ALL, it cancels all predefined tracepoints.
2.10 /TERMINATING
Cancels the effect of a previous SET TRACE/TERMINATING command.
2.11 /USER
Cancels a specified user-defined tracepoint without affecting any predefined tracepoints. This is the default unless you specify /PREDEFINED. To cancel all user-defined tracepoints, use /ALL.
3 – Description
Tracepoints can be user defined or predefined. User-defined tracepoints are explicitly set with the SET TRACE command. Predefined tracepoints, which depend on the type of program you are debugging (for example, Ada or multiprocess), are established automatically when you start the debugger. Use the SHOW TRACE command to identify all tracepoints that are currently set. Any predefined tracepoints are identified as such. User-defined and predefined tracepoints are set and canceled independently. For example, a location or event can have both a user-defined and a predefined tracepoint. Canceling the user- defined tracepoint does not affect the predefined tracepoint, and conversely. To cancel only user-defined tracepoints, do not specify /PREDEFINED with the CANCEL TRACE command (the default is /USER). To cancel only predefined tracepoints, specify /PREDEFINED but not /USER. To cancel both user-defined and predefined tracepoints, use CANCEL TRACE/ALL/USER/PREDEFINED. In general, the effect of CANCEL TRACE is symmetrical with that of SET TRACE (even though SET TRACE is used only with user-defined tracepoints). Thus, to cancel a tracepoint that was established at a specific location, specify that same location (address expression) with CANCEL TRACE. To cancel tracepoints that were established on a class of instructions or events, specify the class of instructions or events with the corresponding qualifier (/LINE, /BRANCH, /ACTIVATING, /EVENT=, and so on). For more information, see the qualifier descriptions. To cause the debugger to temporarily ignore a tracepoint, but retain definition of the tracepoint, use the command DEACTIVATE TRACE. You can later activate the tracepoint (with ACTIVATE TRACE). Related commands: (ACTIVATE,DEACTIVATE,SET,SHOW) TRACE CANCEL ALL (SET,SHOW,CANCEL) BREAK (SET,SHOW) EVENT_FACILITY
4 – Examples
1.DBG> CANCEL TRACE MAIN\LOOP+10 This command cancels the user-defined tracepoint at the location MAIN\LOOP+10. 2.DBG> CANCEL TRACE/ALL This command cancels all user-defined tracepoints. 3.all> CANCEL TRACE/TERMINATING This command cancels a previous SET TRACE/TERMINATING command. As a result, a user-defined tracepoint is not triggered when a process does an image exit. 4.DBG> CANCEL TRACE/EVENT=RUN %TASK 3 This command cancels the tracepoint that was set to trigger when task 3 (task ID = 3) entered the RUN state.