From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-18354-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 20826 invoked by alias); 3 Sep 2002 00:39:05 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 20814 invoked from network); 3 Sep 2002 00:39:01 -0000
Received: from unknown (HELO localhost.redhat.com) (66.30.197.194)
  by sources.redhat.com with SMTP; 3 Sep 2002 00:39:01 -0000
Received: from ges.redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id CA7B73DE5; Mon,  2 Sep 2002 20:39:00 -0400 (EDT)
Message-ID: <3D7404A4.5080504@ges.redhat.com>
Date: Mon, 02 Sep 2002 17:39:00 -0000
From: Andrew Cagney <ac131313@ges.redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/MI testsuite] check for known uiout bugs
References: <Pine.LNX.4.44.0208301511160.1395-100000@valrhona.uglyboxes.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-09/txt/msg00028.txt.bz2

> On Fri, 30 Aug 2002, Andrew Cagney wrote:
> 
> 
>> (I suspect gdb<bugid> is safest :-).  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''.
> 
> 
> How about the below?

See below.

> PS. setup_kfail available? All the references in testsuite were commented 
> out. I've followed them.

Yes.  The patch needs some doco adjustment before going into the master 
sources.

> ChangeLog
> 2002-08-30  Keith Seitz  <keiths@redhat.com>
> 
>         * gdb680.exp: New file to test to check for uiout list/tuple
>         nesting bug.
> 
> "Patch"

This just needs a tweak so that each time it is run it outputs a unique 
test name, something like ``..register-names -1, try N''.  Otherwize, 
yes, ok.

Andrew


> proc do_test {} {
>   mi_gdb_test "-data-list-register-names -1" \
>     {\^error,msg=\"bad register number\"} \
>     "-data-list-register-names -1"
> }
> 
> # Tests a bug with ui-out and nested uiout types. When 
> # an error is encountered building a nest typed, like
> # lists or tuples, the uiout is not reset to some sane
> # state. As a result, uiout still thinks it is building
> # this nested type. Execute enough of these errors and
> # an assertion failure occurs. This is most obvious
> # with invalid register number and the register commands.
> 
> # MAX_UIOUT_LEVELS is set to 5.
> set counter 0
> for {set i 0} {$i < 4} {incr i} {
>   do_test
> }
> 
> #setup_kfail "gdb/680"
> do_test
> 
> mi_gdb_exit
> return 0
> 
>