From: Vladimir Prus <ghost@cs.msu.su>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: -var-list --locals proposal
Date: Sat, 06 Jan 2007 12:28:00 -0000 [thread overview]
Message-ID: <200701061527.37603.ghost@cs.msu.su> (raw)
In-Reply-To: <uodpcz9c3.fsf@gnu.org>
On Saturday 06 January 2007 14:24, Eli Zaretskii wrote:
> > From: Vladimir Prus <ghost@cs.msu.su>
> > Date: Sat, 6 Jan 2007 14:12:54 +0300
> > Cc: gdb@sources.redhat.com
> > >
> > > 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".
> >
> > At the moment, the "KIND" option to -var-list is document as the kind of
> > objects for which varobjs are creates. Say
> >
> > -var-list --registers ...
> >
> > creates varobjs for registers and
> >
> > -var-list --locals
> >
> > will create varobjs for locals. On the contrary,
> >
> > -var-list --frame
> >
> > would be somewhat inconsistent -- it does not create varobjs for frames.
>
> Then perhaps we shouldn't reuse -var-list for this, but instead create
> a new command entirely.
Or use:
-var-list --all-locals-in-frame
? I don't want to introduce too many commands similar commands.
> > > > 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?
> >
> > It might be more efficient. However, different frontend have different ideas
> > how to show local vars. I believe that XCode, for example, shows all
> > locals as soon as you enter the function. Lazy creation would prevent such
> > usage.
>
> We shouldn't punish all front-ends because of what one of them does.
At this point, it's not clear if:
1. Any frontend would need any other behaviour.
2. What the performance overhead would be.
> We could cater to XCode by providing a switch to do what it wants.
I don't think we should introduce switches until a need for such switch
is demonstrated by a frontend that uses the current gdb version
and has some issue with that.
- Volodya
next prev parent reply other threads:[~2007-01-06 12:28 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
2007-01-06 11:14 ` Vladimir Prus
2007-01-06 11:24 ` Eli Zaretskii
2007-01-06 12:28 ` Vladimir Prus [this message]
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=200701061527.37603.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.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