Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Jerome Guitton <guitton@adacore.com>
Subject: Re: [RFA/commit] Memory leak in on reading frame register
Date: Tue, 19 May 2015 10:04:00 -0000	[thread overview]
Message-ID: <555B0AC2.7080506@redhat.com> (raw)
In-Reply-To: <20150515155823.GL4767@adacore.com>

On 05/15/2015 04:58 PM, Joel Brobecker wrote:

>> > Thanks.  I wonder whether the leaks come from constructing the
>> > current frame at each stop, instead of from evaluating
>> > breakpoint conditions.  E.g.., if we do a "step" over:
>> > 
>> >    while (1);
>> > 
>> > ... are we constantly leaking values until the user does
>> > ctrl-c?
>> > 
>> > That would suggest to me to that we should be doing
>> > value_mark/value_free_to_mark around each
>> > handle_inferior_event.
> 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.

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-05-19 10:04 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 [this message]
2015-05-20  7:39           ` pushed: " Joel Brobecker

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=555B0AC2.7080506@redhat.com \
    --to=palves@redhat.com \
    --cc=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