From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20917 invoked by alias); 6 May 2006 01:59:07 -0000 Received: (qmail 20654 invoked by uid 22791); 6 May 2006 01:59:07 -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 01:59:05 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FcC4V-0003Pt-Dl for gdb@sources.redhat.com; Fri, 05 May 2006 21:59:03 -0400 Date: Sat, 06 May 2006 01:59:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: asynchronous MI output commands Message-ID: <20060506015903.GA13095@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <20060506012706.GA25114@brasko.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060506012706.GA25114@brasko.net> 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/msg00041.txt.bz2 On Fri, May 05, 2006 at 09:27:06PM -0400, Bob Rossi wrote: > The first problem that I've run into is determining if an MI output > command is synchronous or asynchronous. I can tell if the MI output > command is asynchronous by looking for, reason="abc", like below, > 47*stopped,reason="end-stepping-range",thread-id="0", ... `ASYNC-RECORD ==>' `EXEC-ASYNC-OUTPUT | STATUS-ASYNC-OUTPUT | NOTIFY-ASYNC-OUTPUT' `EXEC-ASYNC-OUTPUT ==>' `[ TOKEN ] "*" ASYNC-OUTPUT' `STATUS-ASYNC-OUTPUT ==>' `[ TOKEN ] "+" ASYNC-OUTPUT' `NOTIFY-ASYNC-OUTPUT ==>' `[ TOKEN ] "=" ASYNC-OUTPUT' Why can't you tell that output is asynchronous from the *stopped, as opposed to ^done? -- Daniel Jacobowitz CodeSourcery