From: Daniel Jacobowitz <drow@false.org>
To: Karganov Konstantin <kostik@ispras.ru>
Cc: gdb@sources.redhat.com
Subject: Re: MI usage inside a user-defined commands
Date: Thu, 07 Jul 2005 13:03:00 -0000 [thread overview]
Message-ID: <20050707130334.GA3033@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0507071600540.23253-100000@ispserv.ispras.ru>
On Thu, Jul 07, 2005 at 04:06:48PM +0400, Karganov Konstantin wrote:
>
> > The ability to use CLI syntax in MI mode is documented in the manual as
> > an unsupported, transitional feature.
> By the way, the -gdb-set command is described as "Set an internal GDB
> variable. The corresponding GDB command is set".
> From the description it is unclear - is "-gdb-set var" an ocasional
> undocumented feature or the correct way of setting program variables.
>
> I suggest it's better for the docs to state this explicitly.
I don't know the intention - but usually, to manipulate program
variables in MI, one uses varobj.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-07 13:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 12:31 Karganov Konstantin
2005-07-06 13:14 ` Daniel Jacobowitz
2005-07-06 13:46 ` Karganov Konstantin
2005-07-06 13:50 ` Daniel Jacobowitz
2005-07-06 13:57 ` Karganov Konstantin
2005-07-07 12:21 ` Karganov Konstantin
2005-07-07 13:03 ` Daniel Jacobowitz [this message]
2005-07-07 14:16 ` Karganov Konstantin
2005-07-07 21:47 ` Nick Roberts
2005-07-06 21:26 ` Nick Roberts
2005-07-06 21:28 ` Daniel Jacobowitz
2005-07-06 22:50 ` Queries in MI [was Re: MI usage inside a user-defined commands] Nick Roberts
2005-07-06 23:06 ` Daniel Jacobowitz
2005-07-06 23:46 ` Bob Rossi
2005-07-07 0:33 ` Queries in MI Nick Roberts
2005-07-07 1:34 ` Bob Rossi
2005-07-07 3:32 ` Nick Roberts
2005-07-06 21:41 ` MI usage inside a user-defined commands Bob Rossi
2005-07-06 14:02 Alain Magloire
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=20050707130334.GA3033@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kostik@ispras.ru \
/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