Re: [RFA/MI testsuite] check for known uiout bugs

[Andrew Cagney <ac131313 at ges dot redhat dot com>]

> 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