From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16266 invoked by alias); 6 May 2006 04:06:50 -0000 Received: (qmail 16257 invoked by uid 22791); 6 May 2006 04:06:49 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 06 May 2006 04:06:42 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FcE3x-0003si-C3; Sat, 06 May 2006 00:06:37 -0400 Date: Sat, 06 May 2006 11:49:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Bob Rossi , gdb@sources.redhat.com Subject: Re: asynchronous MI output commands Message-ID: <20060506040637.GA14894@nevyn.them.org> Mail-Followup-To: Nick Roberts , Bob Rossi , gdb@sources.redhat.com References: <20060506012706.GA25114@brasko.net> <20060506015903.GA13095@nevyn.them.org> <20060506031435.GE25114@brasko.net> <17500.8198.679332.240864@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17500.8198.679332.240864@farnswood.snap.net.nz> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00049.txt.bz2 On Sat, May 06, 2006 at 04:03:18PM +1200, Nick Roberts wrote: > Can't you just consider it as output? What would your parser do differently > if it was classed as one or other? > > I think making the output asynchronous just determines how the front end can > interact with GDB, not its content. Correct. I think that "asynchronous" is a loaded term; it has too many meanings, most of which don't apply here. Synchronous output is the response to a command. -- Daniel Jacobowitz CodeSourcery