From: Keith Seitz <keiths@redhat.com>
To: Mo DeJong <supermo@bayarea.net>
Cc: <gdb@sources.redhat.com>
Subject: Re: Problem with MI -var-evaluate-expression command
Date: Thu, 11 Jul 2002 12:43:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0207111238390.26547-100000@makita.cygnus.com> (raw)
In-Reply-To: <20020711121839.275ae39f.supermo@bayarea.net>
On Thu, 11 Jul 2002, Mo DeJong wrote:
> It sounds like that works just fine for a watch window where each
> child will be displayed. I just wonder if that is the only valid use case.
> I am looking at building a scripting interface to the gdb/mi, so I don't need
> watch window semantics just now.
If your input is coming from an automated UI, then it sh/would use -var-*.
On the other hand, if the input were coming from a user, then you would
definately want to use -data-*, e.g., Insight's variable windows use
-var-*, but GDB's console would use -data-* (if it implemented its
commands that way).
Keith
next prev parent reply other threads:[~2002-07-11 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 17:15 Mo DeJong
2002-07-10 17:31 ` Keith Seitz
2002-07-11 12:13 ` Mo DeJong
2002-07-11 12:43 ` Keith Seitz [this message]
[not found] <1026487389.32493.ezmlm@sources.redhat.com>
2002-07-12 11:30 ` Jim Ingham
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=Pine.GSO.4.33.0207111238390.26547-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=supermo@bayarea.net \
/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