From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: -stack-list-locals and children
Date: Tue, 30 Jun 2009 09:42:00 -0000 [thread overview]
Message-ID: <h2cmlu$91u$1@ger.gmane.org> (raw)
In-Reply-To: <200906291213.04817.andre.poenitz@nokia.com>
André Pönitz wrote:
> On Monday 29 June 2009 11:39:27 Vladimir Prus wrote:
>> > One point was always to reduce the number of roundtrips before
>> > being able to display the variable view. I think that's a valid point
>> > also from a KDevelop angle of view.
>>
>> Right, but how variable type is helping? Is it used *just* to populate
>> the "type" field in variable view? Or is it also involved in QtCreator's
>> pretty-printing mechanisms somehow?
>
> Right. They are also primary information for the current incarnation of
> Qt Creator's pretty-printing.
>
> However I don't want center the argumentation around the needs of
> a specific IDE though if there is a "cross-IDE" reason. And reducing
> roundtrip count should be fairly cross-IDE ;-}
To summarise yesterday's IRC discussion and today's commits:
1. -stack-list-locals --simple-values does print type.
2. -stack-list-arguments did not accept --simple-values, but instead
accepted a numerical '2' to mean the same. I've now checked in a patch
to make it accept --simple-values as well.
3. Making -stack-list-locals and -stack-list-arguments always print
the type is a simple -- does it seem desirable? I would
say yes, unless we expect frontend to do some other mechanism to discover
types of complex variables.
- Volodya
next prev parent reply other threads:[~2009-06-30 9:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 19:03 Niko Sams
2009-06-28 19:31 ` Vladimir Prus
2009-06-28 19:56 ` Niko Sams
2009-06-29 5:26 ` Vladimir Prus
2009-06-29 7:13 ` Niko Sams
[not found] ` <629542d40906290012p33c5504pde20ddcd7da3474a@mail.gmail.com>
2009-06-29 8:18 ` Vladimir Prus
2009-06-29 9:30 ` Niko Sams
2009-06-29 9:45 ` Vladimir Prus
2009-06-29 11:49 ` Nick Roberts
2009-06-29 7:42 ` André Pönitz
2009-06-29 8:13 ` Nick Roberts
2009-06-29 8:37 ` André Pönitz
2009-06-29 9:33 ` Niko Sams
2009-06-30 10:14 ` Nick Roberts
2009-06-29 15:34 ` Pawel Piech
2009-06-29 16:40 ` Vladimir Prus
2009-06-29 16:55 ` Vladimir Prus
2009-06-29 22:46 ` Nick Roberts
2009-06-29 23:07 ` Pawel Piech
2009-06-30 3:26 ` Pawel Piech
2009-06-29 8:59 ` Vladimir Prus
2009-06-29 9:32 ` André Pönitz
2009-06-29 9:39 ` Vladimir Prus
2009-06-29 10:13 ` André Pönitz
2009-06-30 9:42 ` Vladimir Prus [this message]
2009-06-29 9:36 ` Niko Sams
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='h2cmlu$91u$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--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