From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23698 invoked by alias); 22 Nov 2005 12:13:20 -0000 Received: (qmail 23691 invoked by uid 22791); 22 Nov 2005 12:13:19 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao02.cox.net (HELO eastrmmtao02.cox.net) (68.230.240.37) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Nov 2005 12:13:17 +0000 Received: from white ([68.9.65.164]) by eastrmmtao02.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051122121212.FJXW8508.eastrmmtao02.cox.net@white>; Tue, 22 Nov 2005 07:12:12 -0500 Received: from bob by white with local (Exim 3.36 #1 (Debian)) id 1EeX14-0005Vp-00; Tue, 22 Nov 2005 07:12:54 -0500 Date: Tue, 22 Nov 2005 12:13:00 -0000 From: Bob Rossi To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: MI: asynchronous operation details Message-ID: <20051122121254.GB21117@white> Mail-Followup-To: Vladimir Prus , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00472.txt.bz2 On Tue, Nov 22, 2005 at 11:30:04AM +0300, Vladimir Prus wrote: > > Hi, > so, in MI mode if I emit "-exec-continue" gdb starts inferiour and > immediately gives me back the prompt, accepting further commands. > > However, I can't: > 1. Understand what commands can meaningfully be issued while the inferior > is running. Say, all data read/write commands are likely to produce > inconsistent results if inferior is running. > 2. Practically figure out which commands can be issued at all. Say, both > -data-evaluate-expression and -exec-continue just hang, returning > nothing. This is with CVS HEAD. > > Do I understand correctly that asynchronous MI just don't exist in CVS HEAD, > and only command prompt loop is asynchronous? Even if so, and fully > asynchronous MI is coming, what's the answer to question (1) above? This is a feature that does not currently work. However, it's possible that Nick Roberts work will address some of this lack of functionality. If not, I'm sure in the future, either I (you) or someone else will eventually get this working. Bob Rossi