From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10434 invoked by alias); 10 Mar 2005 16:23:14 -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 10216 invoked from network); 10 Mar 2005 16:23:02 -0000 Received: from unknown (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68) by sourceware.org with SMTP; 10 Mar 2005 16:23:02 -0000 Received: from 127.0.0.1 (AVG SMTP 7.0.308 [266.7.1]); Thu, 10 Mar 2005 16:23:01 +0000 Received: from mace ([192.168.1.25]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.211); Thu, 10 Mar 2005 16:22:54 +0000 From: "Dave Korn" To: "'Bob Rossi'" Cc: "'Karganov Konstantin'" , "'GDB'" Subject: RE: MI output command error Date: Thu, 10 Mar 2005 16:23:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050310160852.GC14061@white> Message-ID: X-OriginalArrivalTime: 10 Mar 2005 16:22:55.0089 (UTC) FILETIME=[6A1DEE10:01C5258D] X-SW-Source: 2005-03/txt/msg00111.txt.bz2 ----Original Message---- >From: 'Bob Rossi' >Sent: 10 March 2005 16:09 >>> 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? Hell no! Gdb is waiting for input from you. Send it a command - e.g. "info program", which wouldn't need to tell you if the inferior was running or stopped if it was only possible to send gdb commands while the inferior was stopped. Some things are disabled while the inferior is running, others aren't. Blimey, if you aren't aware of that it's no wonder this conversation has been going at cross purposes! Check the documentation, take a look at the -async flag for example. And read the section on "GDB/MI result records", which makes it clear that if you see "^running" that means that an asynchronous operation is under way but not completed. Then read the documentation under "GDB/MI Program control", where it explains that -exec-continue is *asynchronous*. Oh, wait a minute, you must have already read that because you quoted the example from it. Do you actually know what the terms "asynchronous" and "synchronous" mean, or were you just kind of skimming over bits that didn't make any sense to you as you read the docs? cheers, DaveK -- Can't think of a witty .sigline today....