Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, Andrew Cagney <cagney@redhat.com>
Subject: Re: [RFA/mi-testsuite] XFAIL mi*-console.exp
Date: Tue, 02 Apr 2002 17:22:00 -0000	[thread overview]
Message-ID: <3CAA5699.FF4450A@redhat.com> (raw)
In-Reply-To: <20020402200140.A21552@nevyn.them.org>

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


> 
> That's not quite the same thing.  You can run stdio test on a native
> target, and (while GDB never sees the output) DejaGNU will.  I could
> do this instead, though... revised patch attached.
> 
> --
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer
> 
> 2002-04-02  Daniel Jacobowitz  <drow@mvista.com>
> 
>         * gdb.mi/mi-console.exp: Accept native console output as an
>         XFAIL.  Don't run the test if we don't have inferior IO.
>         * gdb.mi/mi0-console.exp: Likewise.
> 
> Index: testsuite/gdb.mi/mi-console.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi-console.exp,v
> retrieving revision 1.7
> diff -u -p -r1.7 mi-console.exp
> --- mi-console.exp      2001/08/19 01:23:43     1.7
> +++ mi-console.exp      2002/04/03 01:00:34
> @@ -79,7 +79,8 @@ gdb_expect {
>      }
>  }
> 
> -gdb_expect {
> +if {![gdb_skip_stdio_test "Hello message"]} {
> +  gdb_expect {
>      -re "@\"H\"\r\n.*@\"e\"\r\n.*@\"l\"\r\n.*@\"l\"\r\n.*@\"o\"\r\n.*@\" \"\r\n.*@\"\\\\\\\\\"\r\n.*@\"\\\\\"\"\r\n.*@\"!\"\r\n.*@\"\\\\r\"\r\n.*@\"\\\\n\"\r\n" {
>         pass "Hello message"
>      }
> @@ -92,11 +93,12 @@ gdb_expect {
>         # multiple event sources to channel the output back through the
>         # MI.
> 
> -       fail "Hello message (known bug)"
> +       xfail "Hello message (known limitation)"
>      }
>      timeout {
>         fail "Hello message (timeout)"
>      }
> +  }
>  }
> 
>  gdb_expect {
> Index: testsuite/gdb.mi/mi0-console.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi0-console.exp,v
> retrieving revision 1.5
> diff -u -p -r1.5 mi0-console.exp
> --- mi0-console.exp     2001/08/19 01:23:43     1.5
> +++ mi0-console.exp     2002/04/03 01:00:34
> @@ -79,7 +79,8 @@ gdb_expect {
>      }
>  }
> 
> -gdb_expect {
> +if {![gdb_skip_stdio_test "Hello message"]} {
> +  gdb_expect {
>      -re "@\"H\"\r\n.*@\"e\"\r\n.*@\"l\"\r\n.*@\"l\"\r\n.*@\"o\"\r\n.*@\" \"\r\n.*@\"\\\\\\\\\"\r\n.*@\"\\\\\"\"\r\n.*@\"!\"\r\n.*@\"\\\\r\"\r\n.*@\"\\\\n\"\r\n" {
>         pass "Hello message"
>      }
> @@ -92,11 +93,12 @@ gdb_expect {
>         # multiple event sources to channel the output back through the
>         # MI.
> 
> -       fail "Hello message (known bug)"
> +       xfail "Hello message (known limitation)"
>      }
>      timeout {
>         fail "Hello message (timeout)"
>      }
> +  }
>  }
> 
>  gdb_expect {


  reply	other threads:[~2002-04-03  1:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 16:42 Daniel Jacobowitz
2002-04-02 16:52 ` Michael Snyder
2002-04-02 17:01   ` Daniel Jacobowitz
2002-04-02 17:22     ` Michael Snyder [this message]
2002-04-02 17:39       ` Daniel Jacobowitz
2002-04-03  6:14         ` Fernando Nasser
2002-04-04  7:15           ` Fernando Nasser
2002-04-04  8:36             ` Daniel Jacobowitz
2002-04-04 11:09             ` Andrew Cagney
2002-04-03 20:27 ` Andrew Cagney
2002-04-03 21:13   ` Daniel Jacobowitz
2002-04-04 13:49     ` Andrew Cagney
2002-04-04 13:53       ` Daniel Jacobowitz
2002-04-06 15:04         ` Andrew Cagney
2002-04-04 16:55       ` Fernando Nasser
2002-04-05  6:49         ` Andrew Cagney
2002-04-05  7:22           ` Fernando Nasser
2002-04-05  7:23 Michael Elizabeth Chastain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CAA5699.FF4450A@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox