cont subcommand for dbx: Continue program execution

Description

The cont subcommand continues the execution of the program from the current stopping point until either the program finishes, another breakpoint is reached, a signal is received that is trapped by the dbx command, or an event occurs (such as a fork, an exec, or a program abend).

If a signal is specified, either by the number specified in the signalnumber argument or by the name specified in the signalname argument, the program continues as if that signal had been received by the focus thread.

If a signal is not specified, the dbx debug program variable $sigblock is set, and a signal caused the debugged program to stop, then the program resumes execution. If a signal is not specified, the dbx debug program variable $sigblock is not set, and a signal caused the debugged program to stop, then typing in the cont command with no signal causes the program to continue as if it had received the original signal.

Signal names are not case-sensitive, and the SIG prefix is optional. If no signal is specified, the program continues as if it had not been stopped.

Usage notes

The cont subcommand can be run only while the dbx debug program is running.

Related information

The step, next, goto, and skip subcommands.