From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22942 invoked by alias); 21 May 2009 16:03:33 -0000 Received: (qmail 22702 invoked by uid 22791); 21 May 2009 16:03:31 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_32,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 May 2009 16:03:27 +0000 Received: (qmail 15149 invoked from network); 21 May 2009 16:03:25 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 21 May 2009 16:03:25 -0000 From: Pedro Alves To: Jan Kratochvil Subject: Re: [patch] Fix gdb.mi internal_error on killing inferior Date: Thu, 21 May 2009 16:03:00 -0000 User-Agent: KMail/1.9.10 Cc: gdb-patches@sourceware.org References: <20090520202749.GA17984@host0.dyn.jankratochvil.net> <200905210142.10924.pedro@codesourcery.com> <20090521084235.GA3217@host0.dyn.jankratochvil.net> In-Reply-To: <20090521084235.GA3217@host0.dyn.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905211703.24047.pedro@codesourcery.com> 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: 2009-05/txt/msg00460.txt.bz2 On Thursday 21 May 2009 09:42:35, Jan Kratochvil wrote: > On Thu, 21 May 2009 02:42:10 +0200, Pedro Alves wrote: > > This patches fixes your test above for me. I'm running > > the full testsuite on {sync|async}/{remote|native}, after > > having run a few smoke test .exp's and seeing no problem. > > Does it work for you? > > Yes, it fixes the problem I did see. No regressions on my system. Great, many thanks. I've checked it in. My testing looked good too. With the spurious prompt fixed, running the whole testsuite in async mode gives the same results as it used to before these breakages. -- Pedro Alves