This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
Cygwin B20.1 Expect: timeout broken, nonmatching pattern hangs forever
- To: email@example.com
- Subject: Cygwin B20.1 Expect: timeout broken, nonmatching pattern hangs forever
- From: Krist Roginski <firstname.lastname@example.org>
- Date: Mon, 5 Apr 1999 12:30:31 -0700 (PDT)
- CC: email@example.com
- Reply-to: firstname.lastname@example.org
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
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
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++
Thanks for any insight into this problem.
Krist Roginski email@example.com (408) 374-4174 x305
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org