Job Control Commands [ Symbolic Debugger/iX User's Guide ] MPE/iX 5.0 Documentation
Symbolic Debugger/iX User's Guide
Job Control Commands
Table I-6. Job Control Commands
---------------------------------------------------------------------------------------------
| | | |
| Cmd | Syntax | Description |
| | | |
---------------------------------------------------------------------------------------------
| | | |
| c | | Resumes execution after a breakpoint or a |
| | { c } [ location] | signal has been encountered, ignoring the |
| | { continue} | signal, if any. If a location is |
| | | specified, a temporary breakpoint is set at |
| | | that location. |
| | | |
---------------------------------------------------------------------------------------------
| | | |
| C | | Resumes execution after a breakpoint or a |
| | { C } [ location] | signal has been encountered, allowing the |
| | { Continue} | signal, if any, to be received by the child |
| | | process. If a location is specified, a |
| | | temporary breakpoint is set at that |
| | | location. This works the same as the c |
| | | (continue) command on MPE/iX. |
| | | |
---------------------------------------------------------------------------------------------
| | | |
| k | | Terminates the current child process, if |
| | { k } | any. |
| | { kill} | |
---------------------------------------------------------------------------------------------
| | | |
| r | | Lets you run a program as a new child |
| | { r } [ ;info='info string'] | process with an optional info string. If |
| | { run} | you do not enter an info string, the |
| | | debugger uses those supplied with the last |
| | | r(run) command (if any). info string may |
| | | contain a "<" and/or a ">" for redirecting |
| | | standard input and standard output ($STDIN) |
| | | and ($STDOUT). |
| | | |
---------------------------------------------------------------------------------------------
| | | |
| R | | Lets you run a program as a new child |
| | { R } | process with no argument list. If a child |
| | { Run} | process already exists, the debugger asks |
| | | if you want to terminate the child process |
| | | first. The environment for the child |
| | | process is the same as that for the |
| | | debugger. |
| | | |
---------------------------------------------------------------------------------------------
| | | |
| s | | Single steps through a program, executing |
| | { s } [ number] | one source statement or machine instruction |
| | { step} | at a time before pausing and prompting for |
| | | another command. In source mode, one |
| | | source statement is executed; in |
| | | disassembly mode, one machine instruction |
| | | is executed. If a procedure call is |
| | | encountered, the procedure is single |
| | | stepped in the same manner ("stepped |
| | | into"). To execute more than one statement |
| | | or instruction, enter that number as the |
| | | number parameter. |
| | | |
---------------------------------------------------------------------------------------------
Table I-6. Job Control Commands (cont.)
---------------------------------------------------------------------------------------------
| | | |
| Cmd | Syntax | Description |
| | | |
---------------------------------------------------------------------------------------------
| | | |
| S | | Single steps through a program. In source |
| | { S } [ number] | mode, one source statement (or one step of |
| | { Step} | a multiple step statement in HP Pascal or |
| | | HP C) is executed; in disassembly mode, one |
| | | machine instruction is executed (several |
| | | machine instructions might be equivalent to |
| | | one source statement). If a procedure call |
| | | is encountered, it is not "stepped into". |
| | | Instead, execution steps to the statement |
| | | following the call. To execute more than |
| | | one statement or instruction, enter that |
| | | number as the number parameter. |
| | | |
---------------------------------------------------------------------------------------------
MPE/iX 5.0 Documentation