Lines Matching refs:commands
3305 'available for commands and command arguments, e.g. the current '
3329 'commands as if given in a ".pdbrc" file, see Debugger Commands.\n'
3373 ' commands are explained below). The optional *globals* and '
3481 'Debugger Commands\n'
3484 'The commands recognized by the debugger are listed below. Most\n'
3485 'commands can be abbreviated to one or two letters as indicated; '
3490 'Arguments to commands must be separated by whitespace (spaces '
3504 "Commands that the debugger doesn't recognize are assumed to be "
3522 'Multiple commands may be entered on a single line, separated by '
3525 'commands\n'
3528 'applied to separating the commands; the input is split at the '
3542 'Changed in version 3.2: ".pdbrc" can now contain commands that\n'
3545 'commands had no effect.\n'
3549 ' Without argument, print the list of available commands. With '
3564 ' most commands.\n'
3592 ' number to which all the other breakpoint commands refer.\n'
3655 'commands [bpnumber]\n'
3657 ' Specify a list of commands for breakpoint number *bpnumber*. '
3659 ' commands themselves appear on the following lines. Type a '
3661 ' containing just "end" to terminate the commands. An example:\n'
3663 ' (Pdb) commands 1\n'
3668 ' To remove all commands from a breakpoint, type commands and '
3670 ' it immediately with "end"; that is, give no commands.\n'
3672 ' With no *bpnumber* argument, commands refers to the last '
3676 ' You can use breakpoint commands to start your program up '
3702 ' then continue. If none of the other commands print anything, '
3868 ' typed at the pdb prompt. Note that internal pdb commands '
