From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20921-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 16962 invoked by alias); 13 Mar 2005 20:22:51 -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 16936 invoked from network); 13 Mar 2005 20:22:45 -0000
Received: from unknown (HELO viper.snap.net.nz) (202.37.101.8)
  by sourceware.org with SMTP; 13 Mar 2005 20:22:45 -0000
Received: from farnswood.snap.net.nz (p89-tnt1.snap.net.nz [202.124.110.89])
	by viper.snap.net.nz (Postfix) with ESMTP id A6003498CF4;
	Mon, 14 Mar 2005 09:22:43 +1300 (NZDT)
Received: by farnswood.snap.net.nz (Postfix, from userid 501)
	id D02EC62FC2; Sun, 13 Mar 2005 20:14:13 +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: <16948.40725.317349.246550@farnswood.snap.net.nz>
Date: Sun, 13 Mar 2005 20:22:00 -0000
To: Daniel Jacobowitz <drow@false.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, Eli Zaretskii <eliz@gnu.org>,
	dave.korn@artimi.com, kostik@ispras.ru, gdb@sources.redhat.com
Subject: Re: MI output command error
In-Reply-To: <20050313154027.GA18342@nevyn.them.org>
References: <16946.1979.617105.196894@farnswood.snap.net.nz>
	<20050311213042.GA14428@nevyn.them.org>
	<16946.4725.343793.980977@farnswood.snap.net.nz>
	<01c526ed$Blat.v2.4$2b933720@zahav.net.il>
	<16948.2374.864364.458035@farnswood.snap.net.nz>
	<20050313154027.GA18342@nevyn.them.org>
X-SW-Source: 2005-03/txt/msg00148.txt.bz2

 > > Using MI:
 > > 
 > > -target-select remote localhost:1234
 > > ^connected,thread-id="0",frame={addr="0x400012e0",func="??",args=[]}
 > > (gdb) 
 > > 111-exec-continue
 > > 111^running
 > > (gdb) 
 > > -exec-interrupt
 > > 
 > > The MI command -exec-interrupt does not reach GDB
 > > 
 > > -target-select async localhost:1234
 > > ^connected,thread-id="0",frame={addr="0x400012e0",func="??",args=[]}
 > > (gdb) 
 > > 111-exec-continue
 > > 111^running
 > > (gdb) 
 > > -exec-interrupt
 > > ^done
 > > (gdb) 
 > > -exec-continue
 > > ^error,msg="Cannot execute command exec-continue while target running"
 > > (gdb) 
 > > 
 > > The MI command -exec-interrupt is acknowledged but again the inferior doesn't
 > > actually seem to continue execution and GDB seems to think the target is still
 > > running
 > > 
 > > So it look like the asynchronous operation has been partially implemented.
 > 
 > Are you interested in debugging this problem?  If you are, I will
 > volunteer to add tests for it to the testsuite on platforms which
 > support gdbserver.

At the moment I have some time, so I can offer to try. I will need some hand
holding though. What files should I look at, and what behaviour would you expect?


Nick