Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Mon, 5 Apr 1999 12:30:31 -0700 (PDT)
Message-Id:	<199904051930.MAA24260@mage.surefirev.com.>
From:	Krist Roginski <roginski AT surefirev DOT com>
To:	cygwin AT sourceware DOT cygnus DOT com
CC:	roginski AT appr DOT surefirev DOT com
Subject:	Cygwin B20.1 Expect: timeout broken, nonmatching pattern hangs forever
Reply-to:	roginski AT surefirev DOT com

The "timeout" feature of expect seems to be broken in B20.1.  When a
pattern doesn't match, expect hangs forever.  For example, the
following commands entered interactively at the expect prompt cause it
to hang:

  expect1.1> set timeout 1
  expect1.2> exp_spawn cmd.exe
  expect1.3> expect foo

The string "foo" does not appear in cmd.exe's output, so
expect should time out after 1 second.  Instead it hangs.

I'm running expect.exe from the cygwin B20.1 release.
(h-i586-cygwin32\bin\expect.exe) on Windows NT 4.0.




I have also tried Gordon Chaffee's expect-NT port
(http://bmrc.berkeley.edu/people/chaffee/expectnt.html).
It works on the example above if I use his -pipes option
to exp_spawn.  I hesitate to switch to Gordon's port because:

  1. his expect sources are older (5.21 vs. 5.26 in cygwin b20.1)
  2. he uses visual c++.

Number 2 is the main problem.  I have a large amount of C source code
in my application as well as other Tcl extensions, have it all
compiling nicely under gcc and prefer not to maintain a visual c++
port.


Thanks for any insight into this problem.



___________________________________________________________
Krist Roginski  roginski AT surefirev DOT com  (408) 374-4174 x305







--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -