This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/13310] New: (cpychecher) Suspected memory leak ingdb/python/py-param.c: call_doc_function()
- From: "dmalcolm at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 17 Oct 2011 20:17:01 +0000
- Subject: [Bug python/13310] New: (cpychecher) Suspected memory leak ingdb/python/py-param.c: call_doc_function()
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13310
Bug #: 13310
Summary: (cpychecher) Suspected memory leak in
gdb/python/py-param.c: call_doc_function()
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: dmalcolm@redhat.com
Classification: Unclassified
Created attachment 6012
--> http://sourceware.org/bugzilla/attachment.cgi?id=6012
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.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.