summaryrefslogtreecommitdiff
path: root/Include
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2003-03-23 17:52:28 +0000
committerTim Peters <tim.peters@gmail.com>2003-03-23 17:52:28 +0000
commit7571a0fbcf6fd5d6014008f566f970c84cff7d95 (patch)
tree4d9d82af5dc1b2aa4b51a89648dce4c188c237f5 /Include
parenta16b21fb0ab25e4cbe54fe0a39da5e448f3d44cb (diff)
downloadcpython-git-7571a0fbcf6fd5d6014008f566f970c84cff7d95.tar.gz
Improved new Py_TRACE_REFS gimmicks.
Arranged that all the objects exposed by __builtin__ appear in the list of all objects. I basically peed away two days tracking down a mystery leak in sys.gettotalrefcount() in a ZODB app (== tons of code), because the object leaking the references didn't appear in the sys.getobjects(0) list. The object happened to be False. Now False is in the list, along with other popular & previously missing leak candidates (like None). Alas, we still don't have a choke point covering *all* Python objects, so the list of all objects may still be incomplete.
Diffstat (limited to 'Include')
-rw-r--r--Include/object.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/Include/object.h b/Include/object.h
index 89445c0976..3ac75380a2 100644
--- a/Include/object.h
+++ b/Include/object.h
@@ -582,7 +582,7 @@ PyAPI_FUNC(void) _Py_NewReference(PyObject *);
PyAPI_FUNC(void) _Py_ForgetReference(PyObject *);
PyAPI_FUNC(void) _Py_Dealloc(PyObject *);
PyAPI_FUNC(void) _Py_PrintReferences(FILE *);
-PyAPI_FUNC(void) _Py_AddToAllObjects(PyObject *);
+PyAPI_FUNC(void) _Py_AddToAllObjects(PyObject *, int force);
#else
/* Without Py_TRACE_REFS, there's little enough to do that we expand code