summaryrefslogtreecommitdiffstats
path: root/Lib/pdb.py
Commit message (Collapse)AuthorAgeFilesLines
* Whitespace normalization. Ugh, we really need to do this more often.Neal Norwitz2007-04-251-3/+3
| | | | You might want to review this change as it's my first time. Be gentle. :-)
* Patch #1429539: pdb now correctly initializes the __main__ module forGeorg Brandl2007-03-131-9/+16
| | | | | the debugged script, which means that imports from __main__ work correctly now.
* Patch #1393667: pdb now has a "run" command which restarts the debuggedGeorg Brandl2007-03-131-3/+32
| | | | Python program, optionally with different arguments.
* Patch #1192590: Fix pdb's "ignore" and "condition" commands so they trap the ↵Collin Winter2007-03-111-2/+10
| | | | | | IndexError caused by passing in an invalid breakpoint number. Will backport.
* Add missing "return" statements in exception handler.Georg Brandl2007-03-111-0/+2
|
* Bug #1627316: handle error in condition/ignore pdb commands more gracefully.Georg Brandl2007-01-221-2/+12
|
* [Bug #1526834] Fix crash in pdb when you do 'b f(';Andrew M. Kuchling2006-09-051-1/+1
| | | | | the function name was placed into a regex pattern and the unbalanced paren caused re.compile() to report an error
* Whitespace normalization.Tim Peters2006-07-271-1/+1
|
* Reformat docstring; fix typoAndrew M. Kuchling2006-07-271-1/+2
|
* Patch #721464: pdb.Pdb instances can now be given explicit stdin andGeorg Brandl2006-05-101-95/+98
| | | | | stdout arguments, making it possible to redirect input and output for remote debugging.
* Bug #1472191: convert breakpoint indices to ints before comparing them to intsGeorg Brandl2006-05-031-1/+7
|
* Reindent.Martin v. Löwis2006-04-171-7/+7
|
* Remove bogus character.Martin v. Löwis2006-04-171-1/+1
|
* Patch #790710: Add breakpoint command lists in pdb.Martin v. Löwis2006-04-171-1/+124
|
* bug [ 1192315 ] 'clear -1' in pdbGeorg Brandl2005-08-241-1/+4
|
* Bug #1055168: calling pdb.set_trace() calls Bdb.set_trace, which madeJohannes Gijsbers2004-11-071-1/+1
| | | | | | | the debugger enter inside pdb.set_trace. Patch #1061767: make pdb.set_trace enter enter at the stack frame calling pdb.set_trace().
* SF bug #1052503: pdb runcall should accept keyword argumentsRaymond Hettinger2004-10-241-2/+2
|
* Whitespace normalization.Tim Peters2004-10-121-5/+4
|
* Improvements when running pdb as a script.Johannes Gijsbers2004-10-121-16/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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!
* Patch #1003640: replace checkline() function parsing with new breakpoint logic:Johannes Gijsbers2004-08-301-41/+10
| | | | | | | | | | | | | 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.
* bug #989672: pdb.doc and the help messages for the help_d and help_u methodsJohannes Gijsbers2004-08-141-2/+2
| | | | | 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.
* Replace backticks with repr() or "%r"Walter Dörwald2004-02-121-8/+8
| | | | From SF patch #852334.
* Whitespace normalization.Tim Peters2003-06-151-1/+1
|
* [Bug #741171] pdb crashes when enabling a non-existing breakpointAndrew M. Kuchling2003-05-221-2/+22
| | | | | | | | | 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.
* Detabified.Guido van Rossum2003-04-091-20/+5
| | | | Removed dead code.
* - New function sys.call_tracing() allows pdb to debug codeGuido van Rossum2003-04-091-0/+33
| | | | | | recursively. - pdb has a new command, "debug", which lets you step through arbitrary code from the debugger's (pdb) prompt.
* Get rid of many apply() calls.Guido van Rossum2003-02-271-1/+1
|
* I believe this fixesMichael W. Hudson2003-01-311-2/+3
| | | | | | [ 669692 ] pdb user_call breakage What an odd interface! I guess I should have read the docstring, though.
* Duh. The do_EOF() implementation was bogus. Make it more likeGuido van Rossum2003-01-131-3/+5
| | | | do_quit() -- but print a blank line first.
* This is Richie Hindle's patchMichael W. Hudson2002-12-171-0/+26
| | | | | | | | [ 643835 ] Set Next Statement for Python debuggers with a few tweaks by me: adding an unsigned or two, mentioning that not all jumps are allowed in the doc for pdb, adding a NEWS item and a note to whatsnew, and AuCTeX doing something cosmetic to libpdb.tex.
* Implement a `pp' command, which is like `p' except that itBarry Warsaw2002-11-051-6/+21
| | | | pretty-prints the value of its expression argument.
* At Jim Fulton's request, increase the maxstring value of _saferepr toGuido van Rossum2002-09-101-1/+7
| | | | | | a more reasonable value. Backport candidate.
* Whitespace normalization.Tim Peters2002-08-231-1/+1
|
* This is my patchMichael W. Hudson2002-08-151-1/+7
| | | | | | | | [ 587993 ] SET_LINENO killer Remove SET_LINENO. Tracing is now supported by inspecting co_lnotab. Many sundry changes to document and adapt to this change.
* Fix SF bug 579701 (Fernando Pérez); an input line consisting of one orGuido van Rossum2002-07-121-8/+8
| | | | | | | more spaces only crashed pdb. While I was at it, cleaned up some style nits (spaces between function and parenthesis, and redundant parentheses in if statement).
* SF 563203. Replaced 'has_key()' with 'in'.Raymond Hettinger2002-06-011-6/+6
|
* Add exit as alias for quit, as the easiest way to address SF bugGuido van Rossum2002-04-151-1/+4
| | | | | | #543674. Bugfix candidate.
* SF bug #131560: pdb imports 'repr', causing name collisionTim Peters2001-02-091-2/+2
|
* String method conversion.Eric S. Raymond2001-02-091-35/+33
|
* a few more __all__ listsSkip Montanaro2001-02-071-0/+3
|
* I've been using gdb a lot lately -- I'm missing 'bt' as a command inGuido van Rossum2001-01-201-1/+4
| | | | pdb (pdb calls it 'where'). Added 'bt' as an alias for 'where'.
* Whitespace normalization.Tim Peters2001-01-151-883/+883
|
* - Don't hardcode Unix filename syntax when opening ~/.pdbrc.Guido van Rossum2001-01-141-4/+4
| | | | - Conform to standard coding style in a few more places.
* Update the code to better reflect recommended style:Fred Drake2000-12-121-2/+3
| | | | | Use != instead of <> since <> is documented as "obsolescent". Use "is" and "is not" when comparing with None or type objects.
* Spelling fixes supplied by Rob W. W. Hooft. All these are fixes in eitherThomas Wouters2000-07-161-1/+1
| | | | | | | | | | comments, docstrings or error messages. I fixed two minor things in test_winreg.py ("didn't" -> "Didn't" and "Didnt" -> "Didn't"). There is a minor style issue involved: Guido seems to have preferred English grammar (behaviour, honour) in a couple places. This patch changes that to American, which is the more prominent style in the source. I prefer English myself, so if English is preferred, I'd be happy to supply a patch myself ;)
* Sjoerd Mullender:Guido van Rossum2000-03-061-15/+21
| | | | | | | When you set a breakpoint on a function with a multi-line argument list, the breakpoint is actually set on the second line of the arguments instead of the first line of the body. This patch fixes that.
* Actually, the previous batch's comment should have been different;Guido van Rossum2000-02-041-1/+1
| | | | | | | | | | *this* set of patches is Ka-Ping's final sweep: The attached patches update the standard library so that all modules have docstrings beginning with one-line summaries. A new docstring was added to formatter. The docstring for os.py was updated to mention nt, os2, ce in addition to posix, dos, mac.
* More trivial comment -> docstring transformations by Ka-Ping Yee,Guido van Rossum2000-02-041-14/+13
| | | | | | | | | | | | | | | | | | who writes: Here is batch 2, as a big collection of CVS context diffs. Along with moving comments into docstrings, i've added a couple of missing docstrings and attempted to make sure more module docstrings begin with a one-line summary. I did not add docstrings to the methods in profile.py for fear of upsetting any careful optimizations there, though i did move class documentation into class docstrings. The convention i'm using is to leave credits/version/copyright type of stuff in # comments, and move the rest of the descriptive stuff about module usage into module docstrings. Hope this is okay.
* Sjoerd Mullender writes:Guido van Rossum1999-11-031-0/+3
| | | | | | | | | | | | | | | | I regularly find that pdb sets the breakpoint on the wrong line when I try to set a breakpoint on a function. This fixes the problem somewhat. The real problem is that pdb tries to parse the Python source code to find the first executable line. A better way might be to inspect the code object, or even have a variable in the code object co_firstexecutablelineno, but that's too much work. The patch fixes the problem when the first code line after the def statement contains the start *and* end of a triple-quoted string. The code assumed that the end of a triple-quoted string is not on the same line as the start, and so it would skip to the end of the *next* triple-quoted string.
* Pdb.lineinfo(): Don't use os.popen('egrep ...') to find the line inBarry Warsaw1999-09-091-8/+23
| | | | | | the file that a function is defined on. Non-portable to Windows and JPython. Instead, new find_function() uses re module on a similar (simple-minded) pattern.
generated by cgit v0.12 at 2024-11-30 07:42:56 (GMT)