DBG$HELP.HLB  —  DEBUG  CANCEL  BREAK
    Cancels a breakpoint.

    Format

      CANCEL BREAK  [address-expression[, . . . ]]

1  –  Parameters 

 address-expression

    Specifies a breakpoint 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 BREAK/ACTIVATING command.

2.2    /ALL 

    By default, cancels all user-defined breakpoints. When used
    with /PREDEFINED, cancels all predefined breakpoints but no
    user-defined breakpoints. To cancel all breakpoints, use CANCEL
    BREAK/ALL/USER/PREDEFINED.

2.3    /BRANCH 

    Cancels the effect of a previous SET BREAK/BRANCH command.

2.4    /CALL 

    Cancels the effect of a previous SET BREAK/CALL command.

2.5    /EVENT 

       /EVENT=event-name

    Cancels the effect of a previous SET BREAK/EVENT=event-name
    command. Specify the event name (and address expression, if
    any) exactly as specified with the SET BREAK/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 BREAK/EXCEPTION command.

2.7    /HANDLER 

    Cancels the effect of a previous SET BREAK/HANDLER command.

2.8    /INSTRUCTION 

    Cancels the effect of a previous SET BREAK/INSTRUCTION command.

2.9    /LINE 

    Cancels the effect of a previous SET BREAK/LINE command.

2.10    /PREDEFINED 

    Cancels a specified predefined breakpoint without affecting
    any user-defined breakpoints. When used with /ALL, cancels all
    predefined breakpoints.

2.11    /SYSEMULATE 

    (Alpha only) Cancels the effect of a previous SET
    BREAK/SYSEMULATE command.

2.12    /TERMINATING 

    Cancels the effect of a previous SET BREAK/TERMINATING command.

2.13    /UNALIGNED_DATA 

    (Alpha only) Cancels the effect of a previous SET
    BREAK/UNALIGNED_DATA command.

2.14    /USER 

    Cancels a specified user-defined breakpoint without affecting any
    predefined breakpoints. This is the default unless you specify
    /PREDEFINED. To cancel all user-defined breakpoints, use the /ALL
    qualifier.

3  –  Description 

    Breakpoints can be user defined or predefined. User-defined
    breakpoints are set explicitly with the SET BREAK command.
    Predefined breakpoints, which depend on the type of program
    you are debugging (for example, Ada or ZQUIT multiprocess), are
    established automatically when you start the debugger. Use the
    SHOW BREAK command to identify all breakpoints that are currently
    set. Any predefined breakpoints are identified as such.

    User-defined and predefined breakpoints are set and canceled
    independently. For example, a location or event can have both
    a user-defined and a predefined breakpoint. Canceling the user-
    defined breakpoint does not affect the predefined breakpoint, and
    conversely.

    To cancel only user-defined breakpoints, do not specify
    /PREDEFINED with the CANCEL BREAK command (the default is /USER).
    To cancel only predefined breakpoints, specify /PREDEFINED
    but not /USER. To cancel both predefined and user-defined
    breakpoints, specify both /PREDEFINED and /USER.

    In general, the effect of the CANCEL BREAK command is symmetrical
    with that of the SET BREAK command (even though the SET BREAK
    command is used only with user-defined breakpoints). Thus, to
    cancel a breakpoint that was established at a specific location,
    specify that same location (address expression) with the CANCEL
    BREAK command. To cancel breakpoints 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.

    If you want the debugger to ignore a breakpoint without your
    having to cancel it (for example, if you want to rerun the
    program with and without breakpoints), use the DEACTIVATE BREAK
    instead of the CANCEL BREAK command. Later, you can activate the
    breakpoint (with ACTIVATE BREAK).

    Related commands:

       (ACTIVATE,DEACTIVATE) BREAK
       CANCEL ALL
       (SET,SHOW) BREAK
       (SET,SHOW) EVENT_FACILITY
       (SET,SHOW,CANCEL) TRACE

4  –  Examples 

    1.DBG> CANCEL BREAK MAIN\LOOP+10

      This command cancels the user-defined breakpoint set at the
      address expression MAIN\LOOP+10.

    2.DBG> CANCEL BREAK/ALL

      This command cancels all user-defined breakpoints.

    3.DBG> CANCEL BREAK/ALL/USER/PREDEFINED

      This command cancels all user-defined and predefined
      breakpoints.

    4.all> CANCEL BREAK/ACTIVATING

      This command cancels a previous user-defined SET
      BREAK/ACTIVATING command. As a result, the debugger does not
      suspend execution when a new process is brought under debugger
      control.

    5.DBG> CANCEL BREAK/EVENT=EXCEPTION_TERMINATED/PREDEFINED

      This command cancels the predefined breakpoint set on task
      terminations due to unhandled exceptions. This breakpoint
      is predefined for Ada programs and programs that call POSIX
      threads or Ada routines.
Close Help