From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20882-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 21770 invoked by alias); 10 Mar 2005 16:09:13 -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 20886 invoked from network); 10 Mar 2005 16:08:54 -0000
Received: from unknown (HELO lakermmtao12.cox.net) (68.230.240.27)
  by sourceware.org with SMTP; 10 Mar 2005 16:08:54 -0000
Received: from white ([68.9.64.121]) by lakermmtao12.cox.net
          (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP
          id <20050310160849.MDKT2476.lakermmtao12.cox.net@white>;
          Thu, 10 Mar 2005 11:08:49 -0500
Received: from bob by white with local (Exim 3.35 #1 (Debian))
	id 1D9QDU-0003kB-00; Thu, 10 Mar 2005 11:08:52 -0500
Date: Thu, 10 Mar 2005 16:09:00 -0000
From: 'Bob Rossi' <bob@brasko.net>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Karganov Konstantin' <kostik@ispras.ru>,
	'GDB' <gdb@sources.redhat.com>
Subject: Re: MI output command error
Message-ID: <20050310160852.GC14061@white>
Mail-Followup-To: Dave Korn <dave.korn@artimi.com>,
	'Karganov Konstantin' <kostik@ispras.ru>,
	'GDB' <gdb@sources.redhat.com>
References: <20050310144013.GB14061@white> <SERRANOyz5b6KZmcK8r00000026@SERRANO.CAM.ARTIMI.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <SERRANOyz5b6KZmcK8r00000026@SERRANO.CAM.ARTIMI.COM>
User-Agent: Mutt/1.3.28i
X-SW-Source: 2005-03/txt/msg00109.txt.bz2

> > 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?

> 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.

Bob Rossi