From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24028 invoked by alias); 4 May 2008 17:38:53 -0000 Received: (qmail 24012 invoked by uid 22791); 4 May 2008 17:38:52 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 04 May 2008 17:38:35 +0000 Received: (qmail 19243 invoked from network); 4 May 2008 17:38:33 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 4 May 2008 17:38:33 -0000 From: Vladimir Prus To: Daniel Jacobowitz Subject: Re: Fix MI/async testsuite Date: Sun, 04 May 2008 19:02:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: gdb-patches@sourceware.org References: <200805041618.14962.vladimir@codesourcery.com> <20080504171430.GA18323@caradoc.them.org> <20080504172234.GB18323@caradoc.them.org> In-Reply-To: <20080504172234.GB18323@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805042138.02094.vladimir@codesourcery.com> 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-05/txt/msg00180.txt.bz2 On Sunday 04 May 2008 21:22:34 Daniel Jacobowitz wrote: > On Sun, May 04, 2008 at 01:14:30PM -0400, Daniel Jacobowitz wrote: > > Why should we print ^running before we are ready for more input? > > > > *running, yes, soon as the target starts running. But ^running is the > > result of the command and should show up when the command is done, > > shouldn't it? > > Duh, this is because of sync mode, right? Anyway, it seems like "gdb > accepts input after -exec-continue" and "gdb uses *running instead of > ^running" should have the same condition, to avoid this weird output. Well, ideally, ^running should not exist. When gdb is done with a command, it should always print ^done, and since it's done with a command, print a prompt. Unfortunately, right now ^running exists and does something fairly strange: - in sync mode, you get "^running" + "(gdb)" before even trying to resume target - in async mode you get "^running" + random output + "(gdb)" - in async mode when running CLI command, you get "^running" + "^done" This is a mess, but I don't think we should/can fix this mess without going to MI3. - Volodya