Frederic RISS wrote:
> On Mon, 2005-09-05 at 16:23 -0700, David Gravereaux wrote:
>
>>>Dave responded with a possible correction for this bug at:
>>>
>>>http://aspn.activestate.com/ASPN/Mail/Message/expect/2795941
>>>
>>>I tried this, but did not get the output of the extra child
>>>processes of my spawned processes.  I suspect there is more
>>>involved relating to ensuring the child processes are watched
>>>and controlled in the same way the spawned parent is.
>>>
>>>  Jeff Hobbs, The Tcl Guy
>>>  http://www.ActiveState.com/, a division of Sophos
>>
>>
>>The answer for it is in there somewhere.  I found the call to
>>ContinueDebugEvent from a EXIT_PROCESS_DEBUG_EVENT from a child of the
>>spawned process to cause an exception in the child.  I was using net.exe
>>for the testing.
>>
>>I know nothing more..  A possible handle resource thing maybe?
>
>
> Sorry if this is a dumb question, but is expect for windows' source code
> available so that we could try to experiment ourselves ? I searched on
> activestate.com but didn't find anything except old tcl sources and
> binary packages...

ActiveState is in the process of releasing the source code
in a proper form.  The plan is to role it back into a usable
form with the existing unix Expect source base.  The Windows
port is restructured, so this isn't trivial.

However, we have already commited to open sourcing the code.
If you are interested with experimenting, I can make a
package privately available.  We just aren't ready to release
it "wild" because we don't want it to split apart before it
can find a proper open home.

--
   Jeff Hobbs, The Tcl Guy
   http://www.ActiveState.com/, a division of Sophos
_______________________________________________
Expect mailing list
Expect@list...
http://listserv.ActiveState.com/mailman/listinfo/expect