From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16695 invoked by alias); 10 Apr 2008 20:37:14 -0000 Received: (qmail 16687 invoked by uid 22791); 10 Apr 2008 20:37:13 -0000 X-Spam-Check-By: sourceware.org Received: from igw3.br.ibm.com (HELO igw3.br.ibm.com) (32.104.18.26) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 10 Apr 2008 20:36:52 +0000 Received: from mailhub1.br.ibm.com (unknown [9.18.232.109]) by igw3.br.ibm.com (Postfix) with ESMTP id A0BAF3900D4 for ; Thu, 10 Apr 2008 17:23:59 -0300 (BRST) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m3AKadE82920582 for ; Thu, 10 Apr 2008 17:36:46 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m3AKacUF003077 for ; Thu, 10 Apr 2008 17:36:38 -0300 Received: from [9.8.15.212] ([9.8.15.212]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m3AKabfb003035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2008 17:36:37 -0300 Subject: Re: MI testsuite fix From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: Pedro Alves Cc: gdb-patches@sourceware.org In-Reply-To: <200804102102.07722.pedro@codesourcery.com> References: <200804102102.07722.pedro@codesourcery.com> Content-Type: text/plain Date: Thu, 10 Apr 2008 21:42:00 -0000 Message-Id: <1207859802.9173.15.camel@gargoyle> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit 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-04/txt/msg00208.txt.bz2 Thanks for the patch. On Thu, 2008-04-10 at 21:02 +0100, Pedro Alves wrote: > Fixing this leaves me with one MI regression, mi-pending.exp, which is > related to throwing an exception running the exec cleanups, which deletes > the MI token, when it shouldn't. That is fixed by Vladimir's pending > "murder exec cleanup" patch, or when the token in *stopped is removed. > Both will go in very soon. This is still happening on PPC. So i assume this will be fixed with Vladimir's patch as well. There is an additional failure in the MI testsuite (PPC) when running in asynch mode, mi-simplerun.exp and mi2-simplerun.exp, which seems to be an output ordering issue as well. "Correct" output: 220-exec-continue^M 220^running^M (gdb) ^M Hello, World!callme^M callme^M 220*stopped,reason="exited-normally"^M (gdb) ^M PASS: gdb.mi/mi-simplerun.exp: continue to end "Incorrect" output: 220-exec-continue^M 220^running^M Hello, World!callme^M callme^M (gdb) ^M FAIL: gdb.mi/mi-simplerun.exp: continue to end (failed to resume) Correct and incorrect between "" because both ending results are valid. This is not fixed by your latest patch, Pedro. What do you think? Regards, -- Luis Machado Software Engineer IBM Linux Technology Center