This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: variable objects and registers
- From: Vladimir Prus <ghost at cs dot msu dot su>
- To: Nick Roberts <nickrob at snap dot net dot nz>, gdb-patches at sources dot redhat dot com
- Date: Fri, 05 Jan 2007 12:04:19 +0300
- Subject: Re: variable objects and registers
- References: <17782.41205.881283.845357@kahikatea.snap.net.nz> <17802.17932.377094.90049@kahikatea.snap.net.nz>
Nick Roberts wrote:
> > > > I've settled on -var-list. I don't think 'create' clarifies much,
> > > > and this is not user command,
> > >
> > > Except that it doesn't just list existing variable objects but
> > > "creates" new ones.
> >
> > I fact, I'm not sure what duplicated
> >
> > -var-list --locals
> >
> > should do. Create afresh, or just return already created?
>
> Thats a fair point. It should only create new variable objects if
> execution
> enters a new block. That makes -var-list a reasonable name. In the
> manual I should have said "...creates variable objects for the children if
> they do not already exist.".
Yeah. For -var-list, I've modified the manual to say that -var-list tries
to return previously-created varobjs.
For -var-list --registers I did not implement such reusing logic, because
I feel it's not very important performance-wise (yet?). For -var-list --locals,
we'll certainly have reuse of previously-created varobj, though.
- Volodya