From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29056 invoked by alias); 10 Mar 2005 16:13:27 -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 28909 invoked from network); 10 Mar 2005 16:13:20 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 10 Mar 2005 16:13:20 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1D9QHd-0003hs-Qf; Thu, 10 Mar 2005 11:13:09 -0500 Date: Thu, 10 Mar 2005 16:13:00 -0000 From: Daniel Jacobowitz To: Dave Korn , 'Karganov Konstantin' , 'GDB' Subject: Re: MI output command error Message-ID: <20050310161309.GA14175@nevyn.them.org> Mail-Followup-To: Dave Korn , 'Karganov Konstantin' , 'GDB' References: <20050310144013.GB14061@white> <20050310160852.GC14061@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050310160852.GC14061@white> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00110.txt.bz2 On Thu, Mar 10, 2005 at 11:08:52AM -0500, 'Bob Rossi' wrote: > > > That's why I think the output > > > > > > (gdb) > > > 444-exec-continue > > > 444*running > > > 444*stopped... > > > (gdb) > > > > > > is better. > > > > Well, you're wrong. "running" is the output from the exec-continue > > command and it is synchronous: the exec-continue command executes, starts up > > the inferior, prints out "running", and is then complete. At that point the > > inferior is running, but regardless of that, gdb is ready to take more > > commands and so should prompt you. > > It is? It is still busy executing the inferior. I was under the > impression GDB was somehow "busy" while executing the inferior. Is this > not true? Not necessarily; some targets are asynhronous. > > The "stopped" output is an asynchronous > > notification of an event that occurred while the inferior was running, but > > that in no sense makes it output from the "exec-continue" command. > > Well, GDB says that it is output from the -exec-continue command. It's > asyncronous output. That's why the TOKEN 444 is before the *stopped. If it is asynchronous, that presumably means GDB is willing to accept input.... by definition even. -- Daniel Jacobowitz CodeSourcery, LLC