From: "André Pönitz" <apoenitz@trolltech.com>
To: gdb-patches@sourceware.org
Subject: Re: -var-update @
Date: Tue, 01 Apr 2008 14:30:00 -0000 [thread overview]
Message-ID: <200804011613.34684.apoenitz@trolltech.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04290FF9@ecamlmw720.eamcs.ericsson.se>
On Tuesday 01 April 2008 15:23:29 Marc Khouzam wrote:
>
> > As an example I don't need the 'intermediate level' of public/protected/private
> > information for C++ objects, since I do not want to display that anyway.
> > Yet I have to ask for --all-children, wait for the response, parse it, only to
> > discover that it cointains a, say, private and a public block, and ask again
> > for the 'real' children now. So that's two full roundtrips for what could be one...
>
> That is good example of something that would be nice to improve.
> Maybe having a -depth option to the var-list-children command?
I am rarely interested in seeing deeper levels 'immediately',
and if so, it's unlikely that I'd need the same level for all
children. Just having an option to skip the 'access' level
would be nice. The access information could even be listed
in the child items directly, so there would be no loss of
information for the frontend at all...
> In DSF, we always go to a full depth, so we have no real use for having to
> separately query at each level of children.
Honestly, the biggest improvement for me would be 'stateless MI',
i.e. basically '-evaluate-expression' and '-list-children' without
varobjects being created at all.
I live in a almost pure C++ enviroment, so I display a, say,
std::map<int, std::string> as a two-column table, not as
'a bunch of structures containing pointers to each other'
(no offense to std::map<> implementors implied ;-) ).
Stateful varobject do not really help e.g. for getting
a notification when a new key/value pair gets inserted, as
this can basically happen everywhere in the tree.
Of course, I do not expect gdb to do my job in interpreting
the raw structures, but as it stands, some of the available
operations are "too high level" for me as they try to help me
in a way (like automatically creating varobjects, or, say
returning "cooked" data for char* values) that I have a hard
time to "actively ignore" ;-)
Regards,
Andre'
next prev parent reply other threads:[~2008-04-01 14:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 14:54 Vladimir Prus
2008-03-27 5:17 ` Nick Roberts
2008-03-27 7:00 ` Vladimir Prus
2008-03-27 9:54 ` Nick Roberts
2008-03-27 10:38 ` Vladimir Prus
2008-03-27 13:25 ` Marc Khouzam
2008-03-27 13:37 ` Vladimir Prus
2008-03-27 20:58 ` Nick Roberts
2008-03-28 14:32 ` Marc Khouzam
2008-03-28 16:22 ` Vladimir Prus
2008-03-28 16:33 ` Marc Khouzam
2008-04-01 13:37 ` André Pönitz
2008-04-01 13:56 ` Marc Khouzam
2008-04-01 14:30 ` André Pönitz [this message]
2008-04-03 19:10 ` Daniel Jacobowitz
2008-04-03 19:31 ` Daniel Jacobowitz
2008-04-03 20:05 ` Michael Snyder
2008-03-29 5:16 ` Nick Roberts
2008-03-29 6:38 ` Vladimir Prus
2008-03-30 3:54 ` Nick Roberts
2008-04-03 18:55 ` Vladimir Prus
2008-04-03 21:30 ` Nick Roberts
2008-04-04 11:45 ` Vladimir Prus
2008-04-11 22:01 ` Vladimir Prus
2008-04-11 23:22 ` Nick Roberts
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=200804011613.34684.apoenitz@trolltech.com \
--to=apoenitz@trolltech.com \
--cc=gdb-patches@sourceware.org \
/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