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

[Keith Seitz <keiths@redhat.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?
Keith

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

ChangeLog
2002-08-30  Keith Seitz  <keiths@redhat.com>

        * gdb680.exp: New file to test to check for uiout list/tuple
        nesting bug.

"Patch"
# Copyright 2002 Free Software Foundation, Inc.

# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# 
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
# 
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  

# Please email any bugs, comments, and/or additions to this file to:
# bug-gdb@prep.ai.mit.edu

#
# test gdb/680
#

load_lib mi-support.exp
set MIFLAGS "-i=mi"

gdb_exit
if [mi_gdb_start] {
    continue
}

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