From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [mi] -stack-list-arguments --simple-values
Date: Wed, 01 Jul 2009 17:34:00 -0000 [thread overview]
Message-ID: <200907012134.49196.vladimir@codesourcery.com> (raw)
In-Reply-To: <19019.24800.902658.94531@totara.tehura.co.nz>
On Wednesday 01 July 2009 Nick Roberts wrote:
> > This patch makes -stack-list-arguments --simple-values work.
> > It looks like --simple-values (and friends) were accepted for
> > -stack-list-locals, but not for -stack-list-arguments. While
> > the utility of such human friendly spelling is unclear, for
> > a machine interface, it's even more confusing having 1/2
> > of relevant commands accept it.
>
> It's not immediately clear from the manual that SHOW-VALUES from
> -stack-list-arguments and PRINT-VALUES from -stack-list-locals are related.
> -stack-list-arguments takes three arguments while -stack-list-locals only
> takes -one. I think it would be nice to have one command,
> -stack-list-locals-and-args say, that lists both the locals and the arguments
> of the current frame:
It would be nice indeed. However, I have not entirely designed how a frontend
should actually work with locals and arguments, so I did not do anything
like that -- just fixed obvious inconsistency between existing commands.
- Volodya
next prev parent reply other threads:[~2009-07-01 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:39 Vladimir Prus
2009-06-30 13:59 ` Daniel Jacobowitz
2009-07-01 13:13 ` Nick Roberts
2009-07-01 17:34 ` Vladimir Prus [this message]
2009-07-01 17:45 ` Niko Sams
2009-07-02 8:05 ` André Pönitz
2009-07-02 8:13 ` Niko Sams
2009-07-02 9:37 ` Nick Roberts
2009-07-02 10:30 ` Vladimir Prus
2009-07-03 8:33 ` Nick Roberts
2009-07-24 22:07 ` Tom Tromey
2009-07-25 7:21 ` Vladimir Prus
2009-07-26 11:42 ` 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=200907012134.49196.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--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