2001-01-24 00:25:19 +08:00
|
|
|
# -*- ksh -*-
|
|
|
|
#
|
|
|
|
# If you use the GNU debugger gdb to debug the Python C runtime, you
|
|
|
|
# might find some of the following commands useful. Copy this to your
|
|
|
|
# ~/.gdbinit file and it'll get loaded into gdb automatically when you
|
|
|
|
# start it up. Then, at the gdb prompt you can do things like:
|
|
|
|
#
|
|
|
|
# (gdb) pyo apyobjectptr
|
|
|
|
# <module 'foobar' (built-in)>
|
|
|
|
# refcounts: 1
|
|
|
|
# address : 84a7a2c
|
|
|
|
# $1 = void
|
|
|
|
# (gdb)
|
|
|
|
|
|
|
|
# Prints a representation of the object to stderr, along with the
|
|
|
|
# number of reference counts it current has and the hex address the
|
|
|
|
# object is allocated at. The argument must be a PyObject*
|
|
|
|
define pyo
|
2001-01-24 12:18:13 +08:00
|
|
|
print _PyObject_Dump($arg0)
|
2001-01-24 00:25:19 +08:00
|
|
|
end
|
|
|
|
|
|
|
|
# Prints a representation of the object to stderr, along with the
|
|
|
|
# number of reference counts it current has and the hex address the
|
|
|
|
# object is allocated at. The argument must be a PyGC_Head*
|
|
|
|
define pyg
|
2001-01-24 12:18:13 +08:00
|
|
|
print _PyGC_Dump($arg0)
|
2001-01-24 00:25:19 +08:00
|
|
|
end
|
2003-10-04 04:56:15 +08:00
|
|
|
|
2004-04-02 22:51:13 +08:00
|
|
|
# print the local variables of the current frame
|
|
|
|
define pylocals
|
|
|
|
set $_i = 0
|
|
|
|
while $_i < f->f_nlocals
|
|
|
|
if f->f_localsplus + $_i != 0
|
|
|
|
set $_names = co->co_varnames
|
|
|
|
set $_name = PyString_AsString(PyTuple_GetItem($_names, $_i))
|
|
|
|
printf "%s:\n", $_name
|
|
|
|
# side effect of calling _PyObject_Dump is to dump the object's
|
|
|
|
# info - assigning just prevents gdb from printing the
|
|
|
|
# NULL return value
|
|
|
|
set $_val = _PyObject_Dump(f->f_localsplus[$_i])
|
|
|
|
end
|
|
|
|
set $_i = $_i + 1
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2005-01-09 05:56:43 +08:00
|
|
|
# A rewrite of the Python interpreter's line number calculator in GDB's
|
|
|
|
# command language
|
|
|
|
define lineno
|
|
|
|
set $__co = f->f_code
|
|
|
|
set $__lasti = f->f_lasti
|
|
|
|
set $__sz = ((PyStringObject *)$__co->co_lnotab)->ob_size/2
|
|
|
|
set $__p = (unsigned char *)((PyStringObject *)$__co->co_lnotab)->ob_sval
|
|
|
|
set $__li = $__co->co_firstlineno
|
|
|
|
set $__ad = 0
|
|
|
|
while ($__sz-1 >= 0)
|
|
|
|
set $__sz = $__sz - 1
|
|
|
|
set $__ad = $__ad + *$__p
|
|
|
|
set $__p = $__p + 1
|
|
|
|
if ($__ad > $__lasti)
|
|
|
|
break
|
|
|
|
end
|
|
|
|
set $__li = $__li + *$__p
|
|
|
|
set $__p = $__p + 1
|
|
|
|
end
|
|
|
|
printf "%d", $__li
|
|
|
|
end
|
|
|
|
|
2004-11-18 00:04:15 +08:00
|
|
|
# print the current frame - verbose
|
|
|
|
define pyframev
|
|
|
|
pyframe
|
|
|
|
pylocals
|
|
|
|
end
|
|
|
|
|
2004-04-02 22:51:13 +08:00
|
|
|
define pyframe
|
2004-11-18 00:04:15 +08:00
|
|
|
set $__fn = (char *)((PyStringObject *)co->co_filename)->ob_sval
|
|
|
|
set $__n = (char *)((PyStringObject *)co->co_name)->ob_sval
|
2005-01-09 05:56:43 +08:00
|
|
|
printf "%s (", $__fn
|
|
|
|
lineno
|
|
|
|
printf "): %s\n", $__n
|
|
|
|
### Uncomment these lines when using from within Emacs/XEmacs so it will
|
|
|
|
### automatically track/display the current Python source line
|
|
|
|
# printf "%c%c%s:", 032, 032, $__fn
|
|
|
|
# lineno
|
|
|
|
# printf ":1\n"
|
|
|
|
end
|
|
|
|
|
|
|
|
### Use these at your own risk. It appears that a bug in gdb causes it
|
|
|
|
### to crash in certain circumstances.
|
|
|
|
|
|
|
|
#define up
|
|
|
|
# up-silently 1
|
|
|
|
# printframe
|
|
|
|
#end
|
|
|
|
|
|
|
|
#define down
|
|
|
|
# down-silently 1
|
|
|
|
# printframe
|
|
|
|
#end
|
|
|
|
|
|
|
|
define printframe
|
2005-08-13 08:28:41 +08:00
|
|
|
if $pc > PyEval_EvalFrameEx && $pc < PyEval_EvalCodeEx
|
2005-01-09 05:56:43 +08:00
|
|
|
pyframe
|
|
|
|
else
|
|
|
|
frame
|
|
|
|
end
|
2004-04-02 22:51:13 +08:00
|
|
|
end
|
|
|
|
|
2004-04-02 22:53:55 +08:00
|
|
|
# Here's a somewhat fragile way to print the entire Python stack from gdb.
|
|
|
|
# It's fragile because the tests for the value of $pc depend on the layout
|
|
|
|
# of specific functions in the C source code.
|
|
|
|
|
|
|
|
# Explanation of while and if tests: We want to pop up the stack until we
|
|
|
|
# land in Py_Main (this is probably an incorrect assumption in an embedded
|
|
|
|
# interpreter, but the test can be extended by an interested party). If
|
|
|
|
# Py_Main <= $pc <= Py_GetArgcArv is true, $pc is in Py_Main(), so the while
|
|
|
|
# tests succeeds as long as it's not true. In a similar fashion the if
|
2005-01-09 05:56:43 +08:00
|
|
|
# statement tests to see if we are in PyEval_EvalFrame().
|
2004-04-02 22:53:55 +08:00
|
|
|
|
2004-04-02 22:51:13 +08:00
|
|
|
# print the entire Python call stack
|
|
|
|
define pystack
|
|
|
|
while $pc < Py_Main || $pc > Py_GetArgcArgv
|
2004-08-08 04:11:22 +08:00
|
|
|
if $pc > PyEval_EvalFrame && $pc < PyEval_EvalCodeEx
|
2004-04-02 22:51:13 +08:00
|
|
|
pyframe
|
|
|
|
end
|
|
|
|
up-silently 1
|
|
|
|
end
|
|
|
|
select-frame 0
|
|
|
|
end
|
2004-11-18 00:04:15 +08:00
|
|
|
|
|
|
|
# print the entire Python call stack - verbose mode
|
|
|
|
define pystackv
|
|
|
|
while $pc < Py_Main || $pc > Py_GetArgcArgv
|
|
|
|
if $pc > PyEval_EvalFrame && $pc < PyEval_EvalCodeEx
|
|
|
|
pyframev
|
|
|
|
end
|
|
|
|
up-silently 1
|
|
|
|
end
|
|
|
|
select-frame 0
|
|
|
|
end
|