From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2956 invoked by alias); 12 Jan 2009 11:36:04 -0000 Received: (qmail 2948 invoked by uid 22791); 12 Jan 2009 11:36:03 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Jan 2009 11:35:27 +0000 Received: from kahikatea.snap.net.nz (unknown [123.255.31.169]) by viper.snap.net.nz (Postfix) with ESMTP id 8AA063DA2FD; Tue, 13 Jan 2009 00:35:19 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 3EEED8FC6D; Tue, 13 Jan 2009 00:35:16 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18795.10995.345746.155013@kahikatea.snap.net.nz> Date: Mon, 12 Jan 2009 11:36:00 -0000 To: "Marc Khouzam" Cc: "Vladimir Prus" , Subject: RE: Re: MI *stopped event with CLI commands In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEED@ecamlmw720.eamcs.ericsson.se> References: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEC8@ecamlmw720.eamcs.ericsson.se> <18757.63035.269334.203651@kahikatea.snap.net.nz> <6D19CA8D71C89C43A057926FE0D4ADAA04E1BED4@ecamlmw720.eamcs.ericsson.se> <18761.60118.104115.85983@kahikatea.snap.net.nz> <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEED@ecamlmw720.eamcs.ericsson.se> X-IsSubscribed: yes 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: 2009-01/txt/msg00054.txt.bz2 > I could switch to async mode to solve this problem, but > I'm hesitant to do so because it may have side-effects to > DSF-GDB that I may not be aware of. Also very few targets currently support async mode. Linux, remote, Dicos? > Except for this bug, > I'm not too sure on the advantages of async-mode for DSF-GDB. Non-stop mode seems to require async-mode but I'm not sure why it doesn't enable it automatically. > So, if you feel this bug can be fixed, I will probably wait > for the fix, instead of risking going to async-mode. It's not really a bug because CLI execution commands have never generated full MI output in synchronous mode. I think synchronous really means that control stays with the interpreter that issues the execution command until *after* execution has finished. So any MI output, in this case, is really faked output. -- Nick http://www.inet.net.nz/~nickrob