From: Bob Rossi <bob@brasko.net>
To: Jim Ingham <jingham@apple.com>
Cc: Alain Magloire <alain@qnx.com>, Eli Zaretskii <eliz@gnu.org>,
Andrew Cagney <cagney@gnu.org>,
nick@nick.uklinux.net, gdb-patches@sources.redhat.com
Subject: Re: MI handshaking
Date: Wed, 05 Jan 2005 02:34:00 -0000 [thread overview]
Message-ID: <20050105023423.GE25675@white> (raw)
In-Reply-To: <903D3836-89F2-4080-B978-3CFD9868B623@apple.com>
Here is a patch for the MI handshaking code. In case you forgot, here is
how it acts from the client's perspective,
$ ./gdb -i=mi
handshake={stable_protocols={mi2}}
~"GNU gdb 6.3.50.20050105-cvs\n"
~"Copyright 2004 Free Software Foundation, Inc.\n"
~"GDB is free software, covered by the GNU General Public License, and you are\n"
~"welcome to change it and/or distribute copies of it under certain conditions.\n"
~"Type \"show copying\" to see the conditions.\n"
~"There is absolutely no warranty for GDB. Type \"show warranty\" for details.\n"
~"This GDB was configured as \"i686-pc-linux-gnu\"."
~"\n"
~"Setting up the environment for debugging gdb.\n"
&"No symbol table is loaded. Use the \"file\" command.\n"
&"No symbol table is loaded. Use the \"file\" command.\n"
&".gdbinit:8: Error in sourced command file:\n"
&"No breakpoint number 0.\n"
(gdb)
-handshake-info
^done,stable_protocol="2"
(gdb)
There are several things to note from this patch,
1. The new 'handshake-info' command. It is intended to give all the
information that the user selected during the handshaking phase of
the MI protocol. So far the only thing worth showing is the protocol
version that was selected
2. If the GDB being queried was tested with and supports multiple
protocols of MI, then GDB will block waiting for a response.
3. The handshaking protocol is not in the typical MI syntax. Is this
OK?
Finally, the testsuite will have to change before this commit is OK. Any
pointers on how to add the 'handshake={stable_protocols={mi2}}' to every
testcase?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-01-05 2:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200411120344.WAA24018@smtp.ott.qnx.com>
2004-11-12 22:59 ` Andrew Cagney
2004-11-13 9:01 ` Eli Zaretskii
2004-11-13 13:48 ` Bob Rossi
2004-11-17 16:05 ` Alain Magloire
2004-11-17 16:32 ` Bob Rossi
2004-11-18 1:35 ` Alain Magloire
[not found] ` <200411180135.UAA14730@smtp.ott.qnx.com>
2004-11-19 19:23 ` Bob Rossi
2005-01-05 1:36 ` Bob Rossi
2005-01-05 1:51 ` Jim Ingham
2005-01-05 1:53 ` Bob Rossi
2005-01-05 2:01 ` Jim Ingham
2005-01-05 2:34 ` Bob Rossi [this message]
2005-01-05 2:40 ` Bob Rossi
2004-11-17 16:05 ` Alain Magloire
[not found] <200411171514.KAA17361@smtp.ott.qnx.com>
2004-11-17 17:30 ` Eli Zaretskii
2004-11-12 9:54 Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 19:57 Bob Rossi
2004-11-04 19:59 ` Bob Rossi
2004-11-11 20:30 ` Andrew Cagney
2004-11-12 3:44 ` Alain Magloire
2004-11-04 21:28 ` Eli Zaretskii
2004-11-05 16:39 ` Bob Rossi
2004-11-05 17:50 ` Eli Zaretskii
2004-11-05 22:12 ` Bob Rossi
2004-11-06 10:12 ` Eli Zaretskii
2004-11-08 14:49 ` Bob Rossi
2004-11-08 15:01 ` Eli Zaretskii
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=20050105023423.GE25675@white \
--to=bob@brasko.net \
--cc=alain@qnx.com \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jingham@apple.com \
--cc=nick@nick.uklinux.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