Created attachment 6012 [details]
HTML report showing the execution paths that leak memory
See attached HTML report from gcc-python-plugin's cpychecker:
result->ob_refcnt is 1 too high:
It looks to me like the returned "result" object from PyObject_CallMethodObjArgs() is leaking a reference in each of these paths through the function.
Caveat: this static analyzer is relatively immature, so it could be getting it wrong.
Module name: src
Changes by: email@example.com 2011-10-24 11:39:50
gdb : ChangeLog
gdb/python : py-param.c
2011-10-24 Phil Muldoon <firstname.lastname@example.org>
* python/py-param.c (call_doc_function): Correctly deference on
Fixed and committed as documented in Comment #1.