From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25345 invoked by alias); 4 May 2008 19:57:10 -0000 Received: (qmail 25335 invoked by uid 22791); 4 May 2008 19:57:09 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 04 May 2008 19:56:43 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 9BA4F983F0; Sun, 4 May 2008 19:56:41 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 7F0919829E; Sun, 4 May 2008 19:56:41 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JskK8-00049u-Fd; Sun, 04 May 2008 15:56:40 -0400 Date: Sun, 04 May 2008 20:05:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus Cc: gdb-patches@sourceware.org Subject: Re: Fix MI/async testsuite Message-ID: <20080504195640.GA15966@caradoc.them.org> Mail-Followup-To: Vladimir Prus , gdb-patches@sourceware.org References: <200805041618.14962.vladimir@codesourcery.com> <20080504171430.GA18323@caradoc.them.org> <20080504172234.GB18323@caradoc.them.org> <200805042138.02094.vladimir@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200805042138.02094.vladimir@codesourcery.com> User-Agent: Mutt/1.5.17 (2007-12-11) 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-05/txt/msg00184.txt.bz2 On Sun, May 04, 2008 at 09:38:01PM +0400, Vladimir Prus wrote: > 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. For MI2, why can't we leave ^running always followed by a prompt? We fail to accept input at that prompt in sync mode, which is a known bug, but that's life. I don't think having ^result followed by =EVENT followed by (gdb) makes sense, and it's a new broken behavior, not an old one. -- Daniel Jacobowitz CodeSourcery