From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20903-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 4762 invoked by alias); 11 Mar 2005 21:52:19 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 4730 invoked from network); 11 Mar 2005 21:52:15 -0000
Received: from unknown (HELO viper.snap.net.nz) (202.37.101.8)
  by sourceware.org with SMTP; 11 Mar 2005 21:52:15 -0000
Received: from farnswood.snap.net.nz (p54-tnt1.snap.net.nz [202.124.110.54])
	by viper.snap.net.nz (Postfix) with ESMTP id BC50348EAC2;
	Sat, 12 Mar 2005 10:52:13 +1300 (NZDT)
Received: by farnswood.snap.net.nz (Postfix, from userid 501)
	id E540362FBE; Fri, 11 Mar 2005 21:49:41 +0000 (GMT)
From: Nick Roberts <nickrob@snap.net.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16946.4725.343793.980977@farnswood.snap.net.nz>
Date: Fri, 11 Mar 2005 21:52:00 -0000
To: Daniel Jacobowitz <drow@false.org>
Cc: Dave Korn <dave.korn@artimi.com>,
	Karganov Konstantin <kostik@ispras.ru>, GDB <gdb@sources.redhat.com>
Subject: Re: MI output command error
In-Reply-To: <20050311213042.GA14428@nevyn.them.org>
References: <16946.1979.617105.196894@farnswood.snap.net.nz>
	<20050311213042.GA14428@nevyn.them.org>
X-SW-Source: 2005-03/txt/msg00130.txt.bz2

 > > Dave Korn's explanation is very helpful. Considering the MI output to be
 > > asynchronous, makes it much easier to understand. The fact remains,
 > > however, that for native targets at least (the most common
 > > configuration?), operation is synchronous. It leads me to wonder how this
 > > discrepancy arises.
 > 
 > Lack of implementation.  No one's done the work.

Thats understandable. However, given that MI was introduced in GDB 5.0, I
think there should be something in the manual explaining this as it seems to
create a lot of confusion. It needs to be written by someone who understands
the issue i.e not myself. I believe that operation is asynchronous with
certain targets, although I have never managed to create these conditions,
even with gdbserver over TCP.

Nick