Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI & pretty-printing
Date: Tue, 18 Aug 2009 07:19:00 -0000	[thread overview]
Message-ID: <200908180956.33876.vladimir@codesourcery.com> (raw)
In-Reply-To: <m3ocqei9ht.fsf@fleche.redhat.com>

On Monday 17 August 2009 Tom Tromey wrote:

> >>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
> 
> Volodya> Note that at this point, displayed value of the vector switches
> Volodya> to "std::vector of length 2...".  I think we discussed that
> Volodya> such value should not be used inside MI.
> 
> We discussed it but, IIRC, did not come to any agreement about it.

Hmm, I though we decided that some hint to pretty-printers is desirable.
Anyway, let me repeat my point -- the descriptive string is rather long,
so might not fit in variables window. Further, a frontend typically
has some way to display variable type already, so "std::vector" part 
of the string is not helping either. So, I'd much rather have {...} for
all composite types in MI.

> Volodya> Is it expected that if I have varobj with 1 child, then 
> Volodya>    -var-list-children var 10 20
> Volodya> still prints numchild=1 ?
> 
> I don't know.  I suppose we could try to restrict it to children in the
> requested range.

I don't know either. The current behaviour *feels* strange, but then my
WIP patch for kdevelop does not use this field at all, for incremental
fetches. Maybe we can leave it as is, for now.

Any comment on the crash?

- Volodya


> 
> Tom
> 


  reply	other threads:[~2009-08-18  5:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 17:42 Vladimir Prus
2009-07-14  1:55 ` Nick Roberts
2009-07-15 12:19   ` Vladimir Prus
2009-08-06 21:02 ` Tom Tromey
2009-08-07  5:18   ` Vladimir Prus
2009-08-15 20:43   ` Vladimir Prus
2009-08-17 18:48     ` Tom Tromey
2009-08-18  7:19       ` Vladimir Prus [this message]
2009-08-18 18:41         ` Tom Tromey
2009-08-19  6:51           ` Vladimir Prus
2009-08-19 19:50             ` Tom Tromey
2009-08-20  6:04               ` Vladimir Prus
2009-09-05  9:27   ` Vladimir Prus
2009-09-09 22:34     ` Tom Tromey
2009-09-14 11:19       ` 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=200908180956.33876.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb@sources.redhat.com \
    --cc=tromey@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