Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Nick Roberts <nickrob@snap.net.nz>,  gdb-patches@sources.redhat.com
Subject: Re: MI: -var-list-children --simple-values
Date: Wed, 15 Nov 2006 14:55:00 -0000	[thread overview]
Message-ID: <200611151755.02301.vladimir@codesourcery.com> (raw)
In-Reply-To: <20061115144343.GA25165@nevyn.them.org>

On Wednesday 15 November 2006 17:43, Daniel Jacobowitz wrote:
> On Wed, Nov 15, 2006 at 02:50:19PM +0300, Vladimir Prus wrote:
> > On Wednesday 15 November 2006 14:17, Nick Roberts wrote:
> > > ISTR Daniel J wanted --simple-values for consistency with
> > > -stack-list-locals. As it's easy to fix, I suggest doing that.
> >
> > There are many things that are easy to fix, but it does not mean we need
> > to keep unused functionality.
> >
> > Perhaps Dan can comment why he really needed --simple-values.
>
> I felt that it was useful; I still do.  

Why? Especially, why it's better than --all-values. Note that --simple-values 
only don't print values of arrays, structures and unions, and if you check 
c_value_of_variable, you'll see that for structures just a literal string is 
returned, while for array very trivial formatting operation is used.

In other words, --all-values do not involve any complex processing, reading 
data from the target, or anything. What are we trying to save by 
adding --simple-values?

> Takeup of new MI features by 
> IDEs seems to be a very slow process, since many support the system's
> installed GDB (which may be several revisions behind); reports of MI
> features that don't work also seems to be a bit spotty.  So, honestly,
> I wouldn't read too much into it that no one noticed.  It was new in
> GDB 6.4.
>
> > > I also note
> > > a mistake in the error message.  Both are fixed below.
> >
> > I don't see any regression test for this crash. Are you going to
> > provide one?
>
> I'd appreciate it if one of you could do that, yes.  Shame on me, I
> didn't write one at the time.

Heh ;-)

- Volodya


  reply	other threads:[~2006-11-15 14:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611151250.11654.vladimir@codesourcery.com>
2006-11-15 11:21 ` Nick Roberts
2006-11-15 11:50   ` Vladimir Prus
2006-11-15 14:44     ` Daniel Jacobowitz
2006-11-15 14:55       ` Vladimir Prus [this message]
2006-11-15 15:09         ` Daniel Jacobowitz
2006-11-15 16:29           ` Vladimir Prus
2006-11-15 20:29             ` Nick Roberts
2006-11-29  9:35               ` Vladimir Prus
2006-11-29  9:58                 ` Nick Roberts
2006-11-16 15:57             ` Daniel Jacobowitz
2006-11-15 19:55       ` 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=200611151755.02301.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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