Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | split functionality into pystack and pystackv commands. The former will | Skip Montanaro | 2004-11-17 | 1 | -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 name | Michael W. Hudson | 2004-08-07 | 1 | -1/+1 |
| | |||||
* | It would help if I deleted the old pystack! | Skip Montanaro | 2004-04-02 | 1 | -23/+11 |
| | | | | Also, move pystack comment down next to it | ||||
* | include local variables when dumping Python stack trace | Skip Montanaro | 2004-04-02 | 1 | -9/+36 |
| | |||||
* | Add pystack definition to Misc/gdbinit with some explanation of its behavior | Skip Montanaro | 2004-03-01 | 1 | -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 Hylton | 2003-10-03 | 1 | -0/+9 |
| | | | | assuming it is the variable f. | ||||
* | PyObject_Dump() -> _PyObject_Dump() | Barry Warsaw | 2001-01-24 | 1 | -2/+2 |
| | | | | PyGC_Dump() -> _PyGC_Dump() | ||||
* | A few useful definitions if you're using gdb. Copy to ~/.gdbinit to | Barry Warsaw | 2001-01-23 | 1 | -0/+27 |
pull it in automatically. |