diff options
author | Martin v. Löwis <martin@v.loewis.de> | 2006-04-17 17:08:37 (GMT) |
---|---|---|
committer | Martin v. Löwis <martin@v.loewis.de> | 2006-04-17 17:08:37 (GMT) |
commit | bd30f5288112f9c1d8d5ddfd12dffff32f7d2c44 (patch) | |
tree | 9a1ac34deb1eaeb72d060534f955e6bdfc56541d /Doc/lib/libpdb.tex | |
parent | 297bf82920eaa72674df377b5d42b888baea1fde (diff) | |
download | cpython-bd30f5288112f9c1d8d5ddfd12dffff32f7d2c44.zip cpython-bd30f5288112f9c1d8d5ddfd12dffff32f7d2c44.tar.gz cpython-bd30f5288112f9c1d8d5ddfd12dffff32f7d2c44.tar.bz2 |
Patch #790710: Add breakpoint command lists in pdb.
Diffstat (limited to 'Doc/lib/libpdb.tex')
-rw-r--r-- | Doc/lib/libpdb.tex | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/Doc/lib/libpdb.tex b/Doc/lib/libpdb.tex index 6301175..a5b36a6 100644 --- a/Doc/lib/libpdb.tex +++ b/Doc/lib/libpdb.tex @@ -240,6 +240,45 @@ Condition is an expression which must evaluate to true before the breakpoint is honored. If condition is absent, any existing condition is removed; i.e., the breakpoint is made unconditional. +\item[commands \optional{\var{bpnumber}}] + +Specify a list of commands for breakpoint number \var{bpnumber}. The +commands themselves appear on the following lines. Type a line +containing just 'end' to terminate the commands. An example: + +\begin{verbatim} +(Pdb) commands 1 +(com) print some_variable +(com) end +(Pdb) +\end{verbatim} + +To remove all commands from a breakpoint, type commands and +follow it immediately with end; that is, give no commands. + +With no \var{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. + +Specifying any command resuming execution (currently continue, +step, next, return, jump, quit and their abbreviations) terminates +the command 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 which list to execute. + + If you use the 'silent' command in the command list, the +usual message about stopping at a breakpoint is not printed. This may +be desirable for breakpoints that are to print a specific message and +then continue. If none of the other commands print anything, you +see no sign that the breakpoint was reached. + +\versionadded{2.5} + \item[s(tep)] Execute the current line, stop at the first possible occasion |