From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 684 invoked by alias); 22 Nov 2005 09:07:33 -0000 Received: (qmail 670 invoked by uid 22791); 22 Nov 2005 09:07:32 -0000 X-Spam-Check-By: sourceware.org Received: from nproxy.gmail.com (HELO nproxy.gmail.com) (64.233.182.200) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Nov 2005 09:07:29 +0000 Received: by nproxy.gmail.com with SMTP id p48so160044nfa for ; Tue, 22 Nov 2005 01:07:26 -0800 (PST) Received: by 10.48.214.20 with SMTP id m20mr435257nfg; Tue, 22 Nov 2005 01:07:26 -0800 (PST) Received: by 10.48.236.16 with HTTP; Tue, 22 Nov 2005 01:07:26 -0800 (PST) Message-ID: <159126900511220107j13f8efecr@mail.gmail.com> Date: Tue, 22 Nov 2005 09:07:00 -0000 From: Konstantin Karganov To: Vladimir Prus Subject: Re: MI: asynchronous operation details Cc: gdb@sources.redhat.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-IsSubscribed: yes 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/msg00468.txt.bz2 > so, in MI mode if I emit "-exec-continue" gdb starts inferiour and > immediately gives me back the prompt, accepting further commands. Who said it accepts commands? My gdb (6.3) does not. > 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 HE= AD, > and only command prompt loop is asynchronous? Even if so, and fully > asynchronous MI is coming, what's the answer to question (1) above? Actually, MI also works synchonously. So for 1-2 the answer is "There are no such commands." And morover, you cannot issue the command while the inferior is running. Gdb will process the input only when the execution stops. As for me, I always ignore "(gdb)" prompt since it means nothing and made a frontend work with gdb synchronously (I.e. wait for one answer before sending another command.). All this asynchronism in gdb is also a ghost - it looks like it is real but in fact it do not exist :) PS. Try to search this mailing list for "(a)synchronous" or smth alike, you will find the same questions that I asked a year or so ago :) -- Best regards, Konstantin.