Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: -var-list --locals proposal
Date: Sat, 06 Jan 2007 10:39:00 -0000	[thread overview]
Message-ID: <uvejkzbf4.fsf@gnu.org> (raw)
In-Reply-To: <200701052303.59465.ghost@cs.msu.su> (message from Vladimir Prus 	on Fri, 5 Jan 2007 23:03:59 +0300)

> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Fri, 5 Jan 2007 23:03:59 +0300
> 
> I propose to introduce a new command:
> 
> 	-var-list --locals <frame>

As you explain further, this will actually list all variables that are
visible in the current scope.  So a better name for this command would
be something like "-var-list --scope FRAME" or "-var-list --frame FRAME".

> I think that to avoid creating and destroying variable
> objects as we step though inner blocks, -var-list should construct
> varobjs for all variables in all blocks of a function.

Won't lazy creation (on as needed basis) be a better strategy?


  reply	other threads:[~2007-01-06 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 20:04 Vladimir Prus
2007-01-06 10:39 ` Eli Zaretskii [this message]
2007-01-06 11:14   ` Vladimir Prus
2007-01-06 11:24     ` Eli Zaretskii
2007-01-06 12:28       ` Vladimir Prus
2007-01-06 21:51         ` Nick Roberts
2007-01-16  6:57           ` Vladimir Prus
2007-01-10  3:38 ` Daniel Jacobowitz
2007-01-16  7:01   ` Vladimir Prus
2007-01-16  7:18     ` Daniel Jacobowitz
2007-01-16 16:20       ` Vladimir Prus
2007-01-16 22:52         ` Nick Roberts
2007-01-16 23:12           ` Vladimir Prus
2007-01-17  7:54             ` Nick Roberts
2007-01-17 21:34               ` Vladimir Prus

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=uvejkzbf4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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