[docs] [issue28546] Better explain setting pdb breakpoints
Ian Kelling
report at bugs.python.org
Fri Oct 28 08:55:42 EDT 2016
New submission from Ian Kelling:
https://docs.python.org/3.7/library/pdb.html:
"The typical usage to break into the debugger from a running program is to insert
import pdb; pdb.set_trace()
at the location you want to break into the debugger."
A plain read of this says: insert code into a running program.
I can do this just fine in gdb, so when reading this, I wonder
if attaching is explained elsewhere, or what.
Patch to improve this.
----------
assignee: docs at python
components: Documentation
files: iank-v1.patch
keywords: patch
messages: 279601
nosy: docs at python, iank
priority: normal
severity: normal
status: open
title: Better explain setting pdb breakpoints
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file45253/iank-v1.patch
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28546>
_______________________________________
More information about the docs
mailing list