public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "m at bruenink dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14387] New: Memory leak in gdb/python/py-stopevent.c:66
Date: Mon, 23 Jul 2012 11:13:00 -0000 [thread overview]
Message-ID: <bug-14387-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14387
Bug #: 14387
Summary: Memory leak in gdb/python/py-stopevent.c:66
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: m@bruenink.de
Classification: Unclassified
In py-stopevent.c:66 a PyList is created which is than attached to a stop event
by calling create_breakpoint_event_object. This list is never garbage
collected.
Decrementing the reference count to the list after line 83 fixed the problem
for me.
--
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.
next reply other threads:[~2012-07-23 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 11:13 m at bruenink dot de [this message]
2012-08-01 17:00 ` [Bug python/14387] " tromey at redhat dot com
2012-08-01 17:22 ` tromey at redhat dot com
2012-08-15 14:22 ` cvs-commit at gcc dot gnu.org
2012-08-15 14:28 ` tromey 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-14387-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).