Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
74947ac4
Commit
74947ac4
authored
Jan 12, 1998
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Modify command descriptions to use \optional{} instead of ad-hoc markup.
There are still weirdnesses, but less of them.
parent
6c886a8d
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
32 additions
and
32 deletions
+32
-32
Doc/lib/libpdb.tex
Doc/lib/libpdb.tex
+16
-16
Doc/libpdb.tex
Doc/libpdb.tex
+16
-16
No files found.
Doc/lib/libpdb.tex
View file @
74947ac4
...
...
@@ -136,21 +136,20 @@ but the debugger's state is not changed.
\begin{description}
\item
[h(elp)
[\var{command}]
]
\item
[h(elp)
\optional{\var{command}}
]
Without argument, print the list of available commands.
With a
\var
{
command
}
as argument, print help about that command.
``
\code
{
help pdb
}
'' displays the full documentation file; if the
environment variable
\code
{
PAGER
}
is defined, the file is piped
through that command instead. Since the
\var
{
command
}
argument must be
an identifier, ``
\code
{
help exec
}
'' must be entered to get help on the
``
\code
{
!
}
'' command.
Without argument, print the list of available commands. With a
\var
{
command
}
as argument, print help about that command.
\samp
{
help
pdb
}
displays the full documentation file; if the environment variable
\code
{
PAGER
}
is defined, the file is piped through that command
instead. Since the
\var
{
command
}
argument must be an identifier,
\samp
{
help exec
}
must be entered to get help on the
\samp
{
!
}
command.
\item
[w(here)]
Print a stack trace, with the most recent frame at the bottom.
An arrow indicates the current frame, which determines the
context of
most commands.
Print a stack trace, with the most recent frame at the bottom.
An
arrow indicates the current frame, which determines the context of
most commands.
\item
[d(own)]
...
...
@@ -162,7 +161,8 @@ Move the current frame one level down in the stack trace
Move the current frame one level up in the stack trace
(to a newer frame).
\item
[b(reak) [\var{lineno}\code{|}\var{function}]
[, "
\var
{
condition
}
"]]
\item
[b(reak)
\optional
{
\var
{
lineno
}{
\Large\code
{
|
}}
\var
{
function
}
%
\optional
{
,
\code
{
'
}
\var
{
condition
}
\code
{
'
}}}
]
With a
\var
{
lineno
}
argument, set a break there in the current
file. With a
\var
{
function
}
argument, set a break at the entry of
...
...
@@ -171,7 +171,7 @@ If a second argument is present, it is a string (included in string
quotes!) specifying an expression which must evaluate to true before
the breakpoint is honored.
\item
[cl(ear)
[\var{lineno}]
]
\item
[cl(ear)
\optional{\var{lineno}}
]
With a
\var
{
lineno
}
argument, clear that break in the current file.
Without argument, clear all breaks (but first ask confirmation).
...
...
@@ -198,7 +198,7 @@ Continue execution until the current function returns.
Continue execution, only stop when a breakpoint is encountered.
\item
[l(ist)
[\var{first}]
[,
\var
{
last
}
]
]
\item
[l(ist)
\optional{\var{first\optional{, last}}}
]
List source code for the current file. Without arguments, list 11
lines around the current line or continue the previous listing. With
...
...
@@ -216,7 +216,7 @@ Evaluate the \var{expression} in the current context and print its
value. (Note:
\code
{
print
}
can also be used, but is not a debugger
command --- this executes the Python
\code
{
print
}
statement.)
\item
[
[!]
\var
{
statement
}
]
\item
[
\optional{!}
\var{statement}]
Execute the (one-line)
\var
{
statement
}
in the context of
the current stack frame.
...
...
@@ -241,7 +241,7 @@ The program being executed is aborted.
Some changes were made to the interpreter:
\begin{itemize}
\item
sys.settrace(func)
sets the global trace function
\item
\code
{
sys.settrace(
\var
{
func
}
)
}
sets the global trace function
\item
there can also a local trace function (see later)
\end{itemize}
...
...
Doc/libpdb.tex
View file @
74947ac4
...
...
@@ -136,21 +136,20 @@ but the debugger's state is not changed.
\begin{description}
\item
[h(elp)
[\var{command}]
]
\item
[h(elp)
\optional{\var{command}}
]
Without argument, print the list of available commands.
With a
\var
{
command
}
as argument, print help about that command.
``
\code
{
help pdb
}
'' displays the full documentation file; if the
environment variable
\code
{
PAGER
}
is defined, the file is piped
through that command instead. Since the
\var
{
command
}
argument must be
an identifier, ``
\code
{
help exec
}
'' must be entered to get help on the
``
\code
{
!
}
'' command.
Without argument, print the list of available commands. With a
\var
{
command
}
as argument, print help about that command.
\samp
{
help
pdb
}
displays the full documentation file; if the environment variable
\code
{
PAGER
}
is defined, the file is piped through that command
instead. Since the
\var
{
command
}
argument must be an identifier,
\samp
{
help exec
}
must be entered to get help on the
\samp
{
!
}
command.
\item
[w(here)]
Print a stack trace, with the most recent frame at the bottom.
An arrow indicates the current frame, which determines the
context of
most commands.
Print a stack trace, with the most recent frame at the bottom.
An
arrow indicates the current frame, which determines the context of
most commands.
\item
[d(own)]
...
...
@@ -162,7 +161,8 @@ Move the current frame one level down in the stack trace
Move the current frame one level up in the stack trace
(to a newer frame).
\item
[b(reak) [\var{lineno}\code{|}\var{function}]
[, "
\var
{
condition
}
"]]
\item
[b(reak)
\optional
{
\var
{
lineno
}{
\Large\code
{
|
}}
\var
{
function
}
%
\optional
{
,
\code
{
'
}
\var
{
condition
}
\code
{
'
}}}
]
With a
\var
{
lineno
}
argument, set a break there in the current
file. With a
\var
{
function
}
argument, set a break at the entry of
...
...
@@ -171,7 +171,7 @@ If a second argument is present, it is a string (included in string
quotes!) specifying an expression which must evaluate to true before
the breakpoint is honored.
\item
[cl(ear)
[\var{lineno}]
]
\item
[cl(ear)
\optional{\var{lineno}}
]
With a
\var
{
lineno
}
argument, clear that break in the current file.
Without argument, clear all breaks (but first ask confirmation).
...
...
@@ -198,7 +198,7 @@ Continue execution until the current function returns.
Continue execution, only stop when a breakpoint is encountered.
\item
[l(ist)
[\var{first}]
[,
\var
{
last
}
]
]
\item
[l(ist)
\optional{\var{first\optional{, last}}}
]
List source code for the current file. Without arguments, list 11
lines around the current line or continue the previous listing. With
...
...
@@ -216,7 +216,7 @@ Evaluate the \var{expression} in the current context and print its
value. (Note:
\code
{
print
}
can also be used, but is not a debugger
command --- this executes the Python
\code
{
print
}
statement.)
\item
[
[!]
\var
{
statement
}
]
\item
[
\optional{!}
\var{statement}]
Execute the (one-line)
\var
{
statement
}
in the context of
the current stack frame.
...
...
@@ -241,7 +241,7 @@ The program being executed is aborted.
Some changes were made to the interpreter:
\begin{itemize}
\item
sys.settrace(func)
sets the global trace function
\item
\code
{
sys.settrace(
\var
{
func
}
)
}
sets the global trace function
\item
there can also a local trace function (see later)
\end{itemize}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment