From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32504 invoked by alias); 10 Mar 2005 21:25:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 32423 invoked from network); 10 Mar 2005 21:25:23 -0000 Received: from unknown (HELO lakermmtao10.cox.net) (68.230.240.29) by sourceware.org with SMTP; 10 Mar 2005 21:25:23 -0000 Received: from white ([68.9.64.121]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050310212519.ZNSU29924.lakermmtao10.cox.net@white>; Thu, 10 Mar 2005 16:25:19 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1D9V9l-0003ur-00; Thu, 10 Mar 2005 16:25:21 -0500 Date: Thu, 10 Mar 2005 21:25:00 -0000 From: Bob Rossi To: Dave Korn , 'Karganov Konstantin' , 'GDB' Subject: Re: MI output command error Message-ID: <20050310212521.GC14742@white> Mail-Followup-To: Dave Korn , 'Karganov Konstantin' , 'GDB' References: <20050310144013.GB14061@white> <20050310160852.GC14061@white> <20050310161309.GA14175@nevyn.them.org> <20050310174408.GE14061@white> <20050310175236.GA8276@nevyn.them.org> <20050310204738.GB14742@white> <20050310210848.GA20315@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050310210848.GA20315@nevyn.them.org> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-03/txt/msg00121.txt.bz2 On Thu, Mar 10, 2005 at 04:08:48PM -0500, Daniel Jacobowitz wrote: > 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"? Annotate 2 > > 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. Thanks for the help, it is *very* much appreciated. Bob Rossi