public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13310] New: (cpychecher) Suspected memory leak in gdb/python/py-param.c: call_doc_function()
Date: Mon, 17 Oct 2011 20:17:00 -0000	[thread overview]
Message-ID: <bug-13310-4717@http.sourceware.org/bugzilla/> (raw)

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.


             reply	other threads:[~2011-10-17 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 20:17 dmalcolm at redhat dot com [this message]
2011-10-17 22:39 ` [Bug python/13310] (cpychecker) " dmalcolm at redhat dot com
2011-10-20 14:25 ` pmuldoon at redhat dot com
2011-10-24 11:40 ` cvs-commit at gcc dot gnu.org
2011-10-24 11:41 ` pmuldoon at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13310-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).