From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3157 invoked by alias); 27 Jun 2008 00:15:04 -0000 Received: (qmail 3128 invoked by uid 22791); 27 Jun 2008 00:15:02 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 27 Jun 2008 00:14:34 +0000 Received: from kahikatea.snap.net.nz (103.60.255.123.dynamic.snap.net.nz [123.255.60.103]) by viper.snap.net.nz (Postfix) with ESMTP id 6E57E3DA82E; Fri, 27 Jun 2008 12:14:26 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id C9F508FC6D; Fri, 27 Jun 2008 12:14:19 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18532.12506.972674.635614@kahikatea.snap.net.nz> Date: Fri, 27 Jun 2008 06:58:00 -0000 To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [MI/RFC] Emit ^running via observer. In-Reply-To: <200806261958.06374.vladimir@codesourcery.com> References: <200806140108.24047.vladimir@codesourcery.com> <200806251835.08864.vladimir@codesourcery.com> <18531.2798.547630.806116@kahikatea.snap.net.nz> <200806261958.06374.vladimir@codesourcery.com> X-Mailer: VM 7.19 under Emacs 22.2.50.3 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00490.txt.bz2 > > The tests appear to fail now. > > Which tests? All three in mi-async.exp, at the moment. I'll look at them more closely to see if they are due to local changes. > With unmodified CVS state, all MI tests pass for me both in sync > and async mode. But indeed, if I make mi-async.exp not force async mode, it > starts to fail.... mi-async.exp is a test for async mode, so is not expected to pass in sync mode. > > SYNC: > > > > r > > &"r\n" > > ~"Starting program: /home/nickrob/myprog \n" > > =thread-created,id="1" > > ^running > > *running,thread-id="all" > > (gdb) > > ~"\n" > > ~"Breakpoint 1, main (argc=1, argv=0xbf961424) at myprog.c:146\n" > > ~"146\tmain (int argc, char **argv) {\n" > > *stopped > > (gdb) > > ... in this way. > > > i.e no reason, frame, file, etc fields. It's important for the console in > > a frontend that the CLI command generates the same MI output as the > > corresponding MI command. > > Of course. This is pre-existing problem, though, and was present in gdb 6.8 > -- except that we did not output neither ^running nor *stopped at all -- so > apparently making mi-async.exp not actually enable async mode is a bit > premature yet. The problem, it appears, is that while the CLI command > executes, 'uiout' is the CLI interpreter's uiout, not MI uiout. I'll > probably won't have time to work on this in next month, so patches welcome. It's not a problem if async mode becomes the default, which is my understanding. In sync mode, t may be possible to switch to the underlying MI interpreter while in "proceed" but I think that using async mode is cleaner and I have no plans to make sync mode work in this way. -- Nick http://www.inet.net.nz/~nickrob