| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
svnmerge from
svn+ssh://pythondev@svn.python.org/python/branches/py3k
........
r83259 | georg.brandl | 2010-07-30 09:03:39 +0200 (Fr, 30 Jul 2010) | 1 line
Clarification.
........
r83261 | georg.brandl | 2010-07-30 09:21:26 +0200 (Fr, 30 Jul 2010) | 1 line
#9230: allow Pdb.checkline() to be called without a current frame, for setting breakpoints before starting debugging.
........
r83264 | georg.brandl | 2010-07-30 10:45:26 +0200 (Fr, 30 Jul 2010) | 1 line
Document the "jump" command in pdb.__doc__, and add a version tag for "until X".
........
r83265 | georg.brandl | 2010-07-30 10:54:49 +0200 (Fr, 30 Jul 2010) | 1 line
#8015: fix crash when entering an empty line for breakpoint commands. Also restore environment properly when an exception occurs during the definition of commands.
........
r83268 | georg.brandl | 2010-07-30 11:23:23 +0200 (Fr, 30 Jul 2010) | 2 lines
Issue #8048: Prevent doctests from failing when sys.displayhook has
been reassigned.
........
r83269 | georg.brandl | 2010-07-30 11:43:00 +0200 (Fr, 30 Jul 2010) | 1 line
#6719: In pdb, do not stop somewhere in the encodings machinery if the source file to be debugged is in a non-builtin encoding.
........
r83271 | georg.brandl | 2010-07-30 11:59:28 +0200 (Fr, 30 Jul 2010) | 1 line
#5727: Restore the ability to use readline when calling into pdb in doctests.
........
r83272 | georg.brandl | 2010-07-30 12:29:19 +0200 (Fr, 30 Jul 2010) | 1 line
#5294: Fix the behavior of pdb "continue" command when called in the top-level debugged frame.
........
r83281 | georg.brandl | 2010-07-30 15:36:43 +0200 (Fr, 30 Jul 2010) | 1 line
Add myself for pdb.
........
|
|
|
|
| |
truncated output.
|
| |
|
|
|
|
|
|
| |
add this to trunk while we're on the way to 2.7rc1.
When fixed this can go into py3k first. Sorry.
|
| |
|
|
|
|
| |
print Nones. Add a test for that.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
frame.f_locals overrides its contents with the real locals which undoes modifications made by the debugging user.
|
|
|
|
| |
commonly installed by gettext.
|
| |
|
| |
|
|
|
|
| |
Initial work by Alexander Belopolsky. See Misc/NEWS in this checkin for details.
|
| |
|
|
|
|
| |
SyntaxWarning as triggered by -3.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
optional: it defaults to the traceback of the exception that is currently
being handled.
|
|
|
|
| |
Not sure if these are the correct values, but save_stdout has to be set before its usage...
|
|
|
|
| |
exec call and when creating a recursive instance.
|
|
|
|
| |
You might want to review this change as it's my first time. Be gentle. :-)
|
|
|
|
|
| |
the debugged script, which means that imports from __main__ work
correctly now.
|
|
|
|
| |
Python program, optionally with different arguments.
|
|
|
|
|
|
| |
IndexError caused by passing in an invalid breakpoint number.
Will backport.
|
| |
|
| |
|
|
|
|
|
| |
the function name was placed into a regex pattern and the unbalanced paren
caused re.compile() to report an error
|
| |
|
| |
|
|
|
|
|
| |
stdout arguments, making it possible to redirect input and output
for remote debugging.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
the debugger enter inside pdb.set_trace.
Patch #1061767: make pdb.set_trace enter enter at the stack frame
calling pdb.set_trace().
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fixes:
* Use fresh copy of globals/locals so the script being debugged can't access
the pdb namespace (e.g.: p line_prefix will no longer work).
* Remove pdb.py's path from sys.path. Having it in there is normally not a
problem, but it could prove irritating when messing with PYTHONPATH or
invoking pdb via /usr/bin/pdf.
* You can now set a breakpoint on the script being debugged, even if the script
doesn't end with a '.py' extension. Also, setting breakpoints with absolute
paths now works reliably.
Enhancements:
* Go directly to the first line of the script.
* Enter post-mortem debugging if the script being debugged doesn't catch an
exception.
* Restart the script being debugged and preserve debugger state when the script
being debugged exits.
Cleanup:
* Moved the __main__ method into a main() function.
* Kill the (undocumented, not in __all__) mainmodule/mainpyfile globals, add a
mainpyfile attribute to pdb.
Thanks Ilya Sandler for the patch!
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) When a breakpoint is set via a function name:
- the breakpoint gets the lineno of the def statement
- a new funcname attribute is attached to the breakpoint
2) bdb.effective() calls new function checkfuncname() to handle:
- def statement is executed: don't break.
- a first executable line of a function with a breakpoint on the lineno of the
def statement is reached: break.
This fixes bugs 976878, 926369 and 875404. Thanks Ilya Sandler.
|
|
|
|
|
| |
of the pdb.Pdb class gives have been corrected. d(own) goes to a newer frame,
u(p) to an older frame, not the other way around.
|
|
|
|
| |
From SF patch #852334.
|
| |
|
|
|
|
|
|
|
|
|
| |
Check the supplied breakpoint number more carefully.
(Incompatibility: before this patch, "enable -1" would enable
the last breakpoint on the list; now -1 is not a legal ID. Not sure
anyone would ever use negative indices...)
2.2 bugfix candidate, assuming making -1 illegal isn't considered a problem.
|
|
|
|
| |
Removed dead code.
|
|
|
|
|
|
| |
recursively.
- pdb has a new command, "debug", which lets you step through
arbitrary code from the debugger's (pdb) prompt.
|