Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: BarrRobot <robert@rwall.plus.com>
To: gdb@sourceware.org
Subject: MI Interface - interpretation of value returned by -stack-list-locals (C++)
Date: Sat, 26 Mar 2011 16:36:00 -0000	[thread overview]
Message-ID: <31246347.post@talk.nabble.com> (raw)


The value returned by "-stack-list-locals 1" (inter alia) is of the form:

^done,locals=[{name="variable",value="a quoted string"}....]

i.e. a List of Tuples containing Results. 

When "variable" of the first Result is a 'complex' type - typically an
instantiated class, the quoted string Value of the second appears to be
exactly the same (with allowance for escaped characters) as that produced by
the equivalent console interface (CLI) command and whilst parts of it
conform to the MI output specification, other parts - I am thinking of the
representation of arrays - do not. Is there an intention to present the
entire output of these commands in the defined MI output syntax, and if not,
what is the recommended way to handle this part of the output, i.e. is it
the expectation to present it 'as is' to the user, or is it safe to attempt
to parse out the component parts and their values with rules derived from
the CLI output?

[The thread "[mi] -stack-list-arguments --simple-values" by Vladimir Prus-3
Jun 30, 2009; 10:39am seems vaguely relevant].
-- 
View this message in context: http://old.nabble.com/MI-Interface---interpretation-of-value-returned-by--stack-list-locals-%28C%2B%2B%29-tp31246347p31246347.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.


             reply	other threads:[~2011-03-26 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 16:36 BarrRobot [this message]
2011-03-28  6:13 ` André Pönitz
2011-03-29 14:58 ` Tom Tromey
2011-03-29 15:31   ` BarrRobot
2011-03-29 15:31   ` BarrRobot
2011-03-30 13:50     ` Tom Tromey
2011-04-09 11:50       ` Dodji Seketeli
2011-04-13 13:57         ` Tom Tromey
2011-03-30 14:05   ` Eran Ifrah

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=31246347.post@talk.nabble.com \
    --to=robert@rwall.plus.com \
    --cc=gdb@sourceware.org \
    /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