Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: GDB <gdb@sources.redhat.com>
Cc: cagney@gnu.org
Subject: question on mi-console.exp kfail case
Date: Thu, 10 Feb 2005 04:47:00 -0000	[thread overview]
Message-ID: <20050210023356.GA27218@white> (raw)

Hi,

Andrew, I've mailed you personally cause I think you originally wrote
the comment below,

I've got the entire testsuite passing with the new syntax checker for
the MI output. However, I noticed the testcase mi?-console.exp has this,

   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"
       }
       -re "Hello" {

       # Probably a native system where GDB doesn't have direct
       # control over the inferior console.
       # For this to work, GDB would need to run the inferior process
       # under a PTY and then use the even-loops ability to wait on
       # multiple event sources to channel the output back through the
       # MI.

       kfail "gdb/623" "Hello message"
       }
       timeout {
       fail "Hello message (timeout)"
       }
   }

In particular, I don't know what the first regular expression is, and
it's the one that allows for a "pass". What is it trying to match?

When I run this testcase, I get,
   KFAIL: gdb.mi/mi-console.exp: Hello message (PRMS: gdb/623)

The output of the inferior is simply "Hello \"!\r\n". Since I have the
testsuite set up so the inferior output is redirected to it's own pty,
would it be fine for me to match the expected output with a PASS?

Or is this a kfail for some reason I just don't understand?

Thanks,
Bob Rossi


             reply	other threads:[~2005-02-10  2:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10  4:47 Bob Rossi [this message]
2005-02-10 19:38 ` Andrew Cagney

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=20050210023356.GA27218@white \
    --to=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=gdb@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