From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19444 invoked by alias); 13 Mar 2005 20:25:56 -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 19422 invoked from network); 13 Mar 2005 20:25:49 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 13 Mar 2005 20:25:49 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1DAZec-0001I9-Q4; Sun, 13 Mar 2005 15:25:38 -0500 Date: Sun, 13 Mar 2005 20:25:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Eli Zaretskii , dave.korn@artimi.com, kostik@ispras.ru, gdb@sources.redhat.com Subject: Re: MI output command error Message-ID: <20050313202538.GA4946@nevyn.them.org> Mail-Followup-To: Nick Roberts , Eli Zaretskii , dave.korn@artimi.com, kostik@ispras.ru, gdb@sources.redhat.com 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> <16948.40725.317349.246550@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16948.40725.317349.246550@farnswood.snap.net.nz> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00149.txt.bz2 On Mon, Mar 14, 2005 at 09:14:13AM +1300, Nick Roberts wrote: > > > 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? Have I mentioned that I don't know anything about MI? :-) I'm afraid I have no advice. I would expect -exec-interrupt to send a signal to the target process, just like GDB's SIGINT handler does. Which isn't perfect, but generally works. -- Daniel Jacobowitz CodeSourcery, LLC