From: Nick Roberts <nickrob@snap.net.nz>
To: Karganov Konstantin <kostik@ispras.ru>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: MI usage inside a user-defined commands
Date: Thu, 07 Jul 2005 21:47:00 -0000 [thread overview]
Message-ID: <17101.41804.380817.748045@farnswood.snap.net.nz> (raw)
In-Reply-To: <Pine.LNX.4.44.0507071750140.26875-100000@ispserv.ispras.ru>
> > I don't know the intention - but usually, to manipulate program
> > variables in MI, one uses varobj.
> I know.
> But it seems too much fuss to create a varobj, assign a value and delete
> it when I need just to raise a flag in a debugged program...
The implementation of -gdb-set currently does use CLI but it is still
presented as an MI command. So, although the implementation might change, I
see no reason for the command itself to disappear. Since the documentation
doesn't suggest it is temporary or should not be used for program variables, I
would use this command if it is more convenient.
Nick
next prev parent reply other threads:[~2005-07-07 21:47 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
2005-07-07 14:16 ` Karganov Konstantin
2005-07-07 21:47 ` Nick Roberts [this message]
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=17101.41804.380817.748045@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=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