From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Jerome Guitton <guitton@adacore.com>
Subject: pushed: [RFA/commit] Memory leak in on reading frame register
Date: Wed, 20 May 2015 07:39:00 -0000 [thread overview]
Message-ID: <20150520073912.GB4695@adacore.com> (raw)
In-Reply-To: <555B0AC2.7080506@redhat.com>
> > A very accurate guess, as it turns out. Condition evaluation
> > is not the problem, here, but indeed, we a couple of calls to
> > handle_inferior in addition to each call to
> > bpstat_check_breakpoint_conditions. The former are responsible
> > for the leak.
> >
> > How about the attached patch?
>
> Looks good to me.
Thank you, Pedro. Patch has been pushed to master.
--
Joel
prev parent reply other threads:[~2015-05-20 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 15:55 Joel Brobecker
2015-05-11 10:55 ` Pedro Alves
2015-05-11 20:53 ` Joel Brobecker
2015-05-12 9:43 ` Pedro Alves
2015-05-15 15:58 ` Joel Brobecker
2015-05-15 22:35 ` Doug Evans
2015-05-16 0:03 ` Joel Brobecker
2015-05-19 10:04 ` Pedro Alves
2015-05-20 7:39 ` Joel Brobecker [this message]
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=20150520073912.GB4695@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
/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