Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Ingham <jingham@apple.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI varobj properties
Date: Wed, 15 Nov 2006 17:48:00 -0000	[thread overview]
Message-ID: <C66606C6-73DB-4E91-AD0F-3777CB1FCE84@apple.com> (raw)
In-Reply-To: <200611151942.14091.vladimir@codesourcery.com>

I did -var-info-path-expression lazily, since these can be pretty long  
strings, and most of the time they aren't used.  So hanging one off  
each varobj when it's not needed seems wasteful.

Jim

On Nov 15, 2006, at 8:42 AM, Vladimir Prus wrote:

>
> It looks like MI has grown way to many ways to report properties of  
> a variable
> object:
>
> 	- When a variable object is created, the gdb response reports some
>           properties (like expression and the number of children).
>         - There's -var-info-expression that returns the expression  
> (basically
>           the same as above) and also language.
>         - There's -var-show-attributes that returns "editable"  
> attribute.
> 	- Apple branch has -var-info-path-expression that returns full  
> expression
>
> This is somewhat complicated, and there are no clear rationale how  
> do get any
> new bit of information.
>
> Except for getting the value of a variable objects, all those  
> properties are
> computed by gdb, and there are no complex algorithms. How about the  
> following
> change:
>
>
>         - The commands that create new variable object always return  
> full
>           list of properties.
>         - There's a new command that also returns the full list of  
> properties
>         - For backward compatibility, existing commands just forward
>           to the new command.
>
> Comments?
>
> - Volodya


  reply	other threads:[~2006-11-15 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 16:42 Vladimir Prus
2006-11-15 17:48 ` Jim Ingham [this message]
2006-11-15 21:02 ` 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=C66606C6-73DB-4E91-AD0F-3777CB1FCE84@apple.com \
    --to=jingham@apple.com \
    --cc=gdb@sources.redhat.com \
    --cc=vladimir@codesourcery.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