From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27497 invoked by alias); 8 May 2012 18:51:39 -0000 Received: (qmail 27489 invoked by uid 22791); 8 May 2012 18:51:38 -0000 X-SWARE-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 May 2012 18:51:24 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M3P00H00W8RIL00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Tue, 08 May 2012 21:51:23 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.210.75]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M3P00G3BWDM5BN0@a-mtaout22.012.net.il>; Tue, 08 May 2012 21:51:23 +0300 (IDT) Date: Tue, 08 May 2012 18:51:00 -0000 From: Eli Zaretskii Subject: Re: GDB/MI and ">" prompts In-reply-to: To: Marc Khouzam Cc: stanshebs@earthlink.net, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83obpy1pad.fsf@gnu.org> References: <83vckviv3b.fsf@gnu.org> <20120419154853.GM25623@adacore.com> <83sjfzitxx.fsf@gnu.org> <83r4vjitnj.fsf@gnu.org> <20120419185329.GO25623@adacore.com> <83mx67ikxm.fsf@gnu.org> <837gx7hhxa.fsf@gnu.org> <83lilg6ysn.fsf@gnu.org> <4F9EBD0D.2090701@earthlink.net> 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: 2012-05/txt/msg00240.txt.bz2 > From: Marc Khouzam > Date: Tue, 8 May 2012 11:39:25 -0400 > > I tried Eli's patch with Eclipse and I didn't see any problems. > > I was concerned that changing to the CLI interpreter for a while > could make us lose some MI events, but it does not seem to be > the case. For example, I tried running a thread that will hit > a breakpoint in 5 seconds; I then got into the 'commands' secondary > prompt and waited for the 5 seconds to pass. The *stopped event > was not reported until I sent the 'end' command and got out > of the secondary prompt. This is the behavior with and without > Eli's patch. So it seems MI events are buffered in that case, > and switching to the CLI interpreter does not make use lose that > event. > > So, it seems ok for an Eclipse perspective. Thanks!