Re: [RFA/mi-testsuite] XFAIL mi*-console.exp

Daniel Jacobowitz
2002-04-03T01:39:13Z

On Tue, Apr 02, 2002 at 05:10:49PM -0800, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> >
> > On Tue, Apr 02, 2002 at 04:40:38PM -0800, Michael Snyder wrote:
> > > Daniel Jacobowitz wrote:
> > > >
> > > > These tests are testing for a feature that exists either nowhere or just in
> > > > simulators and some remote stubs: that the inferior's output goes through
> > > > GDB and is properly encoded by the MI layer. Since support isn't there for
> > > > many remote debugging stubs or for native, I think these two tests should be
> > > > XFAIL'd. Does that make sense, Andrew? If so, OK to commit this?
> > >
> > > There is a dejagnu variable that you can use to see
> > > whether this is supported... lemme see...
> > >
> > > Ah -- here you go. You want to do something like the following:
> > >
> > > if { ![gdb_skip_stdio_test "Hello message"] } then {
> > > do the "hello message" test...
> >
> > Isn't gdb_skip_stdio_test for things where there's no way at all to see
> > the output? grep, grep,...
> > if [target_info exists gdb,noinferiorio] {
>
> Well, yes... and that's only going to be true for remote stubs
> and simulators that don't support sending target output thru the
> gdb console. Isn't that what you want? I'm not familiar with
> these tests.
>
> Do you also need to exclude it from running on natives?
> How about
> if { ![isnative && ![gdb_skip_stdio_test ...

The test is checking that output passes through GDB on its way to the
viewer's eye, basically - checks that MI has the chance to get at it
and quote it up all properly.

Remote stubs that pass output through GDB support this, but native
programs are run on gdb's stdout directly at present. There's no
reason it shouldn't work, though - it just doesn't right now. That's
why I'd rather XFAIL than skip the tests.

--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer