From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2621 invoked by alias); 30 Aug 2002 21:48:10 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2613 invoked from network); 30 Aug 2002 21:48:09 -0000 Received: from unknown (HELO valrhona.uglyboxes.com) (64.1.192.220) by sources.redhat.com with SMTP; 30 Aug 2002 21:48:09 -0000 Received: from localhost.localdomain (IDENT:HCrkh5yRo8I9k6rFbRs/iJ88me+oGV/8@localhost.localdomain [127.0.0.1]) by valrhona.uglyboxes.com (8.11.6/8.11.6) with ESMTP id g7ULooS30833 for ; Fri, 30 Aug 2002 14:50:51 -0700 Date: Fri, 30 Aug 2002 14:51:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: gdb-patches@sources.redhat.com Subject: Re: [RFA/MI testsuite] check for known uiout bugs In-Reply-To: <3D6FE61B.4030009@ges.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-08/txt/msg01053.txt.bz2 On Fri, 30 Aug 2002, Andrew Cagney wrote: > I don't think this belongs in mi-basics.exp. I don't really, either, but I knew someone would offer a better place! ;-) > (I suspect gdb is safest :-). Will do. > Given that it is going to fail the test will need to be able to identify > the exact point where the failure is expected so that it can be marked > with a ``setup_kfail''. Okay. BTW, how would people prefer to see this solved? Right now, as far as I can tell, this only happens in the register functions. I could simply add a call to ui_out_list_end before we return MI_CMD_ERROR, but that seems chintzy. IMO a better approach might be to add a function to ui-out.c to reset this uiout and have captured_mi_execute_command call this reset function on the uiout when MI_CMD_ERROR is encountered. (Or maybe just add something to mi_out_rewind?) What do you think? Keith