summaryrefslogtreecommitdiffstats
path: root/Misc/gdbinit
Commit message (Collapse)AuthorAgeFilesLines
* split functionality into pystack and pystackv commands. The former willSkip Montanaro2004-11-171-4/+19
| | | | | | | 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.
* eval_frame now has a PyAPI-style nameMichael W. Hudson2004-08-071-1/+1
|
* It would help if I deleted the old pystack!Skip Montanaro2004-04-021-23/+11
| | | | Also, move pystack comment down next to it
* include local variables when dumping Python stack traceSkip Montanaro2004-04-021-9/+36
|
* Add pystack definition to Misc/gdbinit with some explanation of its behaviorSkip Montanaro2004-03-011-0/+23
| | | | | and add flag comments to ceval.c and main.c alerting people to the coupling between pystack and the layout of those files.
* A helper to dump info about the current frame,Jeremy Hylton2003-10-031-0/+9
| | | | assuming it is the variable f.
* PyObject_Dump() -> _PyObject_Dump()Barry Warsaw2001-01-241-2/+2
| | | | PyGC_Dump() -> _PyGC_Dump()
* A few useful definitions if you're using gdb. Copy to ~/.gdbinit toBarry Warsaw2001-01-231-0/+27
pull it in automatically.