Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>,
		Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: Value reference counting
Date: Mon, 20 Jul 2009 13:34:00 -0000	[thread overview]
Message-ID: <20090720132650.GA1875@caradoc.them.org> (raw)
In-Reply-To: <200907201022.19758.thiago.bauermann@gmail.com>

On Mon, Jul 20, 2009 at 10:22:19AM -0300, Thiago Jung Bauermann wrote:
> Watchpoints hold their own references to values. Other than that, IMHO if 
> watchpoint code causes values to be leaked, that is a bug, not a special 
> feature which should be respected... WDYT?

Confused by your question :-)

The way free_all_values works is that it's only run after a command.
For instance, a breakpoint command, or a user-typed command.  It's not
run every time we stop the target and do some thinking if the thinking
is not in the form of a command.  So it's possible to get values
created that don't get cleaned up for a while.

Leaked was probably not the right word, just not GC'd promptly.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-07-20 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 19:03 Daniel Jacobowitz
2009-07-17 19:04 ` Tom Tromey
2009-07-17 19:25   ` Daniel Jacobowitz
2009-07-17 22:55     ` Tom Tromey
2009-07-20 13:30     ` Thiago Jung Bauermann
2009-07-20 13:34       ` Daniel Jacobowitz [this message]
2009-07-20 14:57         ` Thiago Jung Bauermann
2009-07-20 17:34       ` Tom Tromey
2009-07-20 19:45         ` Thiago Jung Bauermann
2009-07-20  9:55 ` Vladimir Prus
2009-07-20 13:40   ` Daniel Jacobowitz
2009-07-20 15:08     ` Vladimir Prus
2009-07-21 18:18 ` Daniel Jacobowitz

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=20090720132650.GA1875@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=thiago.bauermann@gmail.com \
    --cc=tromey@redhat.com \
    --cc=vladimir@codesourcery.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