> > From: jeffh@[...].com
...
> > You are welcome to have
> > the source code and try and figure out more in depth why it aborts
> > abruptly on your system. You can find the source code at:
> >
> > ftp://tcl.activestate.com/pub/incoming/expect-src.zip

That's probably the best way to discover why/how the EOF is returned
immediately.  There is a bit of a posix translation problem that disallows
Expect to return platform specific errors, which result in the general and
meaningless EINVAL to be given to the channel API subsystem.  The real error
can be discovered in a step-debugger before it is tossed away by the channel
interface.  See expWinConsoleDebugger.cpp for the deep guts and channel
interface is expWinSpawnClass::Read() in ExpWinSpawnClass.cpp

To be quite honest, reading through the code for the first time in about a
year, I don't see how any errors, except for a graceful close, are handled in
ExpWinSpawnClass::Read() (!?)   The Message class does have a
Message::TYPE_ERROR type, but there is no select case in
ExpWinSpawnClass::Read() to handle it as all that can be returned to the
channel API is a meaningless EINVAL anyways.

If anyone needs help reading the code, I'm available for advice, though I
don't know if can spend much time, if any, doing debug cycles.

-- 
   I imagine bugs and girls have a dim perception that nature played a cruel
trick on them, but they lack the intelligence to really comprehend the
magnitude of it.	  -- Calvin
_______________________________________________
Expect mailing list
Expect@[...].com
http://listserv.ActiveState.com/mailman/listinfo/expect