I have a problem with my debug Python 2.5.2 executable with Py_REF_DEBUG
and Py_TRACE_REFS set. With one of my scripts I get:
...
Fatal Python error: Python/ceval.c:947 object at 0x2aa3f4d840 has negative ref
count -2604246222170760230
Program received signal SIGABRT, Aborted.
[Switching to Thread 182905044128 (LWP 2595)]
0x0000002a95dde479 in raise () from /lib64/tls/libc.so.6
(gdb) p ((PyObject*)0x2aa3f4d840)->ob_type
$1 = (struct _typeobject *) 0xdbdbdbdbdbdbdbdb
(gdb) p ((PyObject*)0x2aa3f4d840)->ob_refcnt
$2 = -2604246222170760230
(gdb) p ((PyObject*)0x2aa3f4d840)->_ob_next
$3 = (struct _object *) 0xdbdbdbdbdbdbdbdb
(gdb) p ((PyObject*)0x2aa3f4d840)->_ob_prev
$4 = (struct _object *) 0xdbdbdbdbdbdbdbdb
(gdb)
Is there any "common" reason to for such a strange object on the command
stack, or is it more likely that any of my extension modules is causing
havoc?
Kind regards
Berthold
--
__ Address:
G / \ L Germanischer Lloyd
phone: +49-40-36149-7374 -+----+- Vorsetzen 35 P.O.Box 111606
fax : +49-40-36149-7320 \__/ D-20459 Hamburg D-20416 Hamburg
--
http://mail.python.org/mailman/listinfo/python-list
