From: Daniel Jacobowitz <drow@false.org>
To: Dave Korn <dave.korn@artimi.com>,
'Karganov Konstantin' <kostik@ispras.ru>,
'GDB' <gdb@sources.redhat.com>
Subject: Re: MI output command error
Date: Thu, 10 Mar 2005 21:10:00 -0000 [thread overview]
Message-ID: <20050310210848.GA20315@nevyn.them.org> (raw)
In-Reply-To: <20050310204738.GB14742@white>
On Thu, Mar 10, 2005 at 03:47:38PM -0500, Bob Rossi wrote:
> > I'm as mystified as Dave as to how you could read the manual and
> > believe GDB/MI was designed to operate synchronously. A number of MI
> > commands have documentation that begins with "Asynchronous command." In
> > particular, look at -exec-interrupt, which makes no sense as a
> > synchronous command.
>
> Hey, I'm still learning here, just make sure you don't confuse
> mystified/stupid :)
>
> I've been used to working with the a2 interace, which wasn't
> asyncronous.
What do you mean by "a2"?
> Do you guys know if the MI always works asyncronously? Or
> are there modes when it has to work syncronously?
_MI_ is defined to be asynchronous. Any asynchronous interface may
appear synchronous under some conditions.
How asynchronous it is depends on the target; most targets are not
fully async.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-10 21:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 2:40 Bob Rossi
2005-03-09 23:22 ` Bob Rossi
2005-03-10 9:33 ` Re[2]: " Konstantin Karganov
2005-03-10 13:06 ` Bob Rossi
2005-03-10 13:43 ` Karganov Konstantin
2005-03-10 14:01 ` Bob Rossi
2005-03-10 14:15 ` Karganov Konstantin
2005-03-10 14:40 ` Bob Rossi
2005-03-10 15:13 ` Karganov Konstantin
2005-03-10 15:52 ` Dave Korn
2005-03-10 16:09 ` 'Bob Rossi'
2005-03-10 16:13 ` Daniel Jacobowitz
2005-03-10 17:44 ` Bob Rossi
2005-03-10 17:52 ` Daniel Jacobowitz
2005-03-10 20:48 ` Bob Rossi
2005-03-10 21:10 ` Daniel Jacobowitz [this message]
2005-03-10 21:25 ` Bob Rossi
2005-03-10 16:23 ` Dave Korn
2005-03-10 16:34 ` Daniel Jacobowitz
2005-03-10 16:48 ` Dave Korn
2005-03-10 17:03 ` 'Bob Rossi'
2005-03-11 11:32 ` Re[2]: " Konstantin Karganov
2005-03-11 21:05 Nick Roberts
2005-03-11 21:31 ` Daniel Jacobowitz
2005-03-11 21:36 ` Bob Rossi
2005-03-11 21:39 ` Daniel Jacobowitz
2005-03-11 21:52 ` Nick Roberts
2005-03-12 10:23 ` Eli Zaretskii
2005-03-13 9:36 ` Nick Roberts
2005-03-13 15:40 ` Daniel Jacobowitz
2005-03-13 20:22 ` Nick Roberts
2005-03-13 20:25 ` Daniel Jacobowitz
2005-03-13 23:33 ` Nick Roberts
2005-03-13 23:38 ` Daniel Jacobowitz
2005-03-13 19:41 ` Eli Zaretskii
2005-03-14 7:16 ` Peter D HUERTER
[not found] <1110656346.18541.ezmlm@sources.redhat.com>
2005-03-14 19:11 ` 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=20050310210848.GA20315@nevyn.them.org \
--to=drow@false.org \
--cc=dave.korn@artimi.com \
--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