diff options
author | Stéphane Wirtel <stephane@wirtel.be> | 2018-01-30 09:34:33 (GMT) |
---|---|---|
committer | Andrew Svetlov <andrew.svetlov@gmail.com> | 2018-01-30 09:34:33 (GMT) |
commit | 67adb31a416864f853772c3e74a06caeadc9b6f1 (patch) | |
tree | b9f2af001c93c37f8278e4455fb5ccf26d0178a7 /Doc/library/pdb.rst | |
parent | 066df4fd454d6ff9be66e80b2a65995b10af174f (diff) | |
download | cpython-67adb31a416864f853772c3e74a06caeadc9b6f1.zip cpython-67adb31a416864f853772c3e74a06caeadc9b6f1.tar.gz cpython-67adb31a416864f853772c3e74a06caeadc9b6f1.tar.bz2 |
bpo-32724: Fix references to commands in Doc/pdb.rst (GH-5444)
Some commands are specified in the documentation, but there is no direct
references.
Diffstat (limited to 'Doc/library/pdb.rst')
-rw-r--r-- | Doc/library/pdb.rst | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst index e81c195..c6720cb 100644 --- a/Doc/library/pdb.rst +++ b/Doc/library/pdb.rst @@ -332,16 +332,19 @@ by the local file. (com) end (Pdb) - To remove all commands from a breakpoint, type commands and follow it + To remove all commands from a breakpoint, type ``commands`` and follow it immediately with ``end``; that is, give no commands. - With no *bpnumber* argument, commands refers to the last breakpoint set. + With no *bpnumber* argument, ``commands`` refers to the last breakpoint set. You can use breakpoint commands to start your program up again. Simply use - the continue command, or step, or any other command that resumes execution. + the :pdbcmd:`continue` command, or :pdbcmd:`step`, + or any other command that resumes execution. - Specifying any command resuming execution (currently continue, step, next, - return, jump, quit and their abbreviations) terminates the command list (as if + Specifying any command resuming execution + (currently :pdbcmd:`continue`, :pdbcmd:`step`, :pdbcmd:`next`, + :pdbcmd:`return`, :pdbcmd:`jump`, :pdbcmd:`quit` and their abbreviations) + terminates the command :pdbcmd:`list` (as if that command was immediately followed by end). This is because any time you resume execution (even with a simple next or step), you may encounter another breakpoint—which could have its own command list, leading to ambiguities about |