Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	drow@false.org, 	gdb-patches@sources.redhat.com
Subject: Re: Ping: frozen variable objects
Date: Sun, 15 Apr 2007 08:04:00 -0000	[thread overview]
Message-ID: <17953.24758.171944.252414@farnswood.snap.net.nz> (raw)
In-Reply-To: <200704141353.51962.vladimir@codesourcery.com>

 > +  if (varobj_get_frozen (var))
 > +    ui_out_field_int (uiout, "frozen", 1);

So the frozen value is implicitly 0 if the field is not printed?  More
importantly,  I don't see how the front end can find out if a simple variable
object (not a child) is frozen or not.  You could say that the front end
should keep track of this, but this would also be an argument against having
a frozen field at all.

-- 
Nick                                           http://www.inet.net.nz/~nickrob



int m[10];

(gdb) 
-var-create - * m
^done,name="var1",numchild="10",value="[10]",type="int [10]"
(gdb) 
-var-set-frozen var1 1

How can I see that var1 is frozen?



Another (related) doc thought:

`-var-set-frozen'             set frozeness attribute

This suggests that -var-show-attributes will display frozenness.


  parent reply	other threads:[~2007-04-14 23:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25  9:52 Vladimir Prus
2007-03-25 20:17 ` Eli Zaretskii
2007-04-10 19:03 ` Daniel Jacobowitz
2007-04-11 14:44   ` Vladimir Prus
2007-04-11 14:52     ` Daniel Jacobowitz
2007-04-11 18:38       ` Eli Zaretskii
2007-04-13  9:53     ` Eli Zaretskii
2007-04-14 16:14       ` Vladimir Prus
2007-04-14 16:19         ` Daniel Jacobowitz
2007-04-14 23:18           ` Nick Roberts
2007-04-15 10:32             ` Vladimir Prus
2007-04-15 10:35             ` Vladimir Prus
2007-04-15 11:46               ` Nick Roberts
2007-04-15 11:57                 ` Vladimir Prus
2007-04-15 20:09                   ` Nick Roberts
2007-04-15 20:16                   ` Eli Zaretskii
2007-04-15 20:13               ` Eli Zaretskii
2007-04-14 20:32         ` Eli Zaretskii
2007-04-15 11:42           ` Vladimir Prus
2007-04-15 12:03             ` Nick Roberts
2007-04-16  2:40               ` Eli Zaretskii
2007-04-18  5:38                 ` Vladimir Prus
2007-04-18 10:37                   ` Nick Roberts
2007-04-18 22:23                     ` Eli Zaretskii
2007-04-19  4:41                   ` Eli Zaretskii
2007-04-15 20:14             ` Eli Zaretskii
2007-04-15  8:04         ` Nick Roberts [this message]
2007-04-18 10:22         ` [patch] fix insight (was: Re: Ping: frozen variable objects) Brian Dessent
2007-04-18 12:51           ` Maciej W. Rozycki
2007-04-18 13:01             ` Brian Dessent
2007-04-18  5:38   ` Ping: frozen variable objects Michael Snyder
2007-04-18  6:57     ` Vladimir Prus
2007-04-18 22:21       ` Michael Snyder

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=17953.24758.171944.252414@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.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