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

[Keith Seitz <keiths@redhat.com>]

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<bugid> 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