Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>, 	gdb-patches@sources.redhat.com
Subject: Re: [MI] -stack-list-variables
Date: Mon, 21 Sep 2009 22:10:00 -0000	[thread overview]
Message-ID: <19127.63969.180199.561232@totara.tehura.co.nz> (raw)
In-Reply-To: <200909212002.44063.vladimir@codesourcery.com>

 > > But what would happen the day a front-end starts caring? Are they
 > > going to have to send 2 MI commands to get the info?
 > 
 > No. The frontend author would write an email to gdb@sources.redhat.com,
 > explaining the reasons, and a new field will be added as result. That's
 > how I'd prefer MI to evolve, as opposed to adding information ahead of
 > the time.

That's exactly what I have done.

and:

> I am frankly surprised by the amount of support for this feature, and
> the fact that this support say this is harmless, and possibly
> useful, but does not name any single frontend that actually separates
> arguments from "true" locals.

I'm not sure that `proof by example' should be necessary. but here's an
example showing Totalview separate the two:

http://upc.lbl.gov/docs/user/ProcessWindow.png

Totalview is probably the world's best C/C++ debugger (apart fron GDB, of
course!).  I'm sure that if their users didn't want this feature, Etnus would
remove it.

As a maintainer I would try to accommodate such requests and reserve my
judgements for technical matters.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  parent reply	other threads:[~2009-09-21 22:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 10:12 Vladimir Prus
2009-09-19 10:13 ` Vladimir Prus
2009-09-19 10:38   ` Eli Zaretskii
2009-09-19 11:15 ` Vladimir Prus
2009-09-19 15:45 ` Joel Brobecker
2009-09-19 15:46 ` Joel Brobecker
2009-09-19 22:41 ` -stack-list-variables Nick Roberts
2009-09-20  6:18   ` [MI] -stack-list-variables Vladimir Prus
2009-09-20 22:05     ` Nick Roberts
2009-09-21  5:14       ` Vladimir Prus
2009-09-21  7:13         ` Nick Roberts
2009-09-21  7:39           ` Vladimir Prus
2009-09-21 15:29         ` Joel Brobecker
2009-09-21 16:02           ` Vladimir Prus
2009-09-21 16:27             ` Joel Brobecker
2009-09-21 16:54               ` Vladimir Prus
2009-09-21 17:04                 ` Tom Tromey
2009-09-21 17:17                   ` Vladimir Prus
2009-09-21 17:24                     ` Tom Tromey
2009-09-21 17:03               ` Marc Khouzam
2009-09-21 22:10             ` Nick Roberts [this message]
2009-09-22  5:31               ` Vladimir Prus
2009-09-22 14:50                 ` Daniel Jacobowitz
2009-09-29  6:35                 ` Vladimir Prus
2009-09-29 23:27                   ` 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=19127.63969.180199.561232@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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