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
ff667a5c
Commit
ff667a5c
authored
Nov 18, 2004
by
Raymond Hettinger
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
SF patch #1068456: small update for pdb docs
parent
a1d6068b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
0 deletions
+7
-0
Doc/lib/libpdb.tex
Doc/lib/libpdb.tex
+7
-0
No files found.
Doc/lib/libpdb.tex
View file @
ff667a5c
...
@@ -42,6 +42,13 @@ a script to debug other scripts. For example:
...
@@ -42,6 +42,13 @@ a script to debug other scripts. For example:
python -m pdb myscript.py
python -m pdb myscript.py
\end{verbatim}
\end{verbatim}
When invoked as a script, pdb will automatically enter post-mortem debugging
if the program being debugged exits abnormally. After post-mortem debugging
(or after normal exit of the program), pdb will restart the program.
Automatic restarting preserves pdb's state (such as breakpoints) and in most
cases is more useful than quitting the debugger upon program's exit.
\versionadded
[Restarting post-mortem behavior added]
{
2.4
}
Typical usage to inspect a crashed program is:
Typical usage to inspect a crashed program is:
\begin{verbatim}
\begin{verbatim}
...
...
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