From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14616 invoked by alias); 5 Sep 2007 06:33:39 -0000 Received: (qmail 14607 invoked by uid 22791); 5 Sep 2007 06:33:38 -0000 X-Spam-Check-By: sourceware.org Received: from zigzag.lvk.cs.msu.su (HELO zigzag.lvk.cs.msu.su) (158.250.17.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Sep 2007 06:33:34 +0000 Received: from Debian-exim by zigzag.lvk.cs.msu.su with spam-scanned (Exim 4.50) id 1ISoSB-0003oR-Id for gdb@sources.redhat.com; Wed, 05 Sep 2007 10:33:31 +0400 Received: from localhost ([127.0.0.1] helo=ip6-localhost) by zigzag.lvk.cs.msu.su with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1ISoS8-0003oG-JR; Wed, 05 Sep 2007 10:33:28 +0400 From: Vladimir Prus To: Nick Roberts Subject: Re: MI Development Date: Wed, 05 Sep 2007 06:33:00 -0000 User-Agent: KMail/1.9.6 Cc: gdb@sources.redhat.com References: <200709041740.22271.ghost@cs.msu.su> <200709050940.18839.ghost@cs.msu.su> <18142.19645.46590.936933@kahikatea.snap.net.nz> In-Reply-To: <18142.19645.46590.936933@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709051033.28029.ghost@cs.msu.su> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-09/txt/msg00034.txt.bz2 On Wednesday 05 September 2007 10:29:17 Nick Roberts wrote: > > > With asynchronous operation, asynchronous CLI commands give the same MI > > > output that MI commands do. > > > > Why would I want to enable asynchronous operation for that to work? The > > default behaviour is just broken, so even if --async fixes that, we should > > not require any switches to get non-broken behaviour. > > My understanding is that currently GDB only operates synchronously (except > perhaps with remote targets). We're talking past each other, I'm afraid :-( I'm saying that currently, "^running" is not output in cases where it definitely should, and that should be fixed. It's not apparent to me why this fix is related to any asynchronous operation, and if so, this should be fixed separately, and as soon as possible -- meaning as soon as I personally find time for that. Do you disagree? - Volodya