Commit Graph

10 Commits

Author SHA1 Message Date
Neil Schemenauer f98e6b15ba Fix pystack command. 2005-08-13 00:28:41 +00:00
Skip Montanaro afd77d980e Add definitions for "up" and "down" commands that print/display the current
Python file/line when the current C execution frame is inside
PyEval_EvalFrame.  These are commented out by default because GDB sometimes
crashes as a result (seems like a GDB bug).

Add a pyframe command that displays the current Python stack frame.  If the
marked lines are uncommented, it will also cause Emacs/XEmacs to display the
current file/line.
2005-01-08 21:56:43 +00:00
Skip Montanaro 0bb2a65dbd split functionality into pystack and pystackv commands. The former will
work with core dumps because it avoids calling any Python API routines.  The
latter prints all the local variable values as well as the stack frames but
won't work with core dumps because it relies on _PyObject_Dump to print
variables.
2004-11-17 16:04:15 +00:00
Michael W. Hudson 8c47f4a657 eval_frame now has a PyAPI-style name 2004-08-07 20:11:22 +00:00
Skip Montanaro 7a92d74c52 It would help if I deleted the old pystack!
Also, move pystack comment down next to it
2004-04-02 14:53:55 +00:00
Skip Montanaro 74d07f2bfa include local variables when dumping Python stack trace 2004-04-02 14:51:13 +00:00
Skip Montanaro 786ea6bc23 Add pystack definition to Misc/gdbinit with some explanation of its behavior
and add flag comments to ceval.c and main.c alerting people to the coupling
between pystack and the layout of those files.
2004-03-01 15:44:05 +00:00
Jeremy Hylton f64ec0f2a1 A helper to dump info about the current frame,
assuming it is the variable f.
2003-10-03 20:56:15 +00:00
Barry Warsaw bbd89b66b1 PyObject_Dump() -> _PyObject_Dump()
PyGC_Dump() -> _PyGC_Dump()
2001-01-24 04:18:13 +00:00
Barry Warsaw 39e44d7a9c A few useful definitions if you're using gdb. Copy to ~/.gdbinit to
pull it in automatically.
2001-01-23 16:25:19 +00:00