traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Stéphane Wirtel 2018-01-30 10:34:33 +01:00 committed by Andrew Svetlov
parent 066df4fd45
commit 67adb31a41
2 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Doc/library/pdb.rst
View File

@ -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

2
Misc/NEWS.d/next/Documentation/2018-01-30-09-00-19.bpo-32724.qPIaM-.rst Normal file
View File

@ -0,0 +1,2 @@
Add references to some commands in the documentation of Pdb. Patch by
Stéphane Wirtel