Hi Gast?n,
Yes you are right, and you have found a way to correct the problem.
When you do OSProcessAccessor initialize, a new child watcher process
will be started, and this will correct any problem in the old one. I
am still curious to discover the cause of the original failure. I suspect
that i
Hi David.
I send some days ago a mail reporting "process never is completed" in
Windows, and I propose similar steps to reproduce, see:
http://forum.world.st/OSProcess-is-process-done-tp4569088p4570740.html
Two notes about this previous mail: Two notes about this previous mail: I
say "the image h
David T. Lewis wrote
>
> Can you please try two things, in this order, and let me know which
> one causes the problem to go away?
>
Thanks, David. I can't reproduce the problem at the moment, but if it pops
up again, I'll try those...
Sean
--
View this message in context:
http://forum.world.
Sean,
Can you please try two things, in this order, and let me know which
one causes the problem to go away?
1) Save your image, exit, and restart. Then try
(OSProcess command: 'ls') inspect
and see if it results in a process proxy with run state "complete".
2) Restart the child watcher
O
With the latest OSProcess package from SqS, when I save the image, I get:
2 May 2012 1:20:30 am
VM: Mac OS - intel - 1073 - Croquet Closure Cog VM [CoInterpreter
VMMaker-oscog-EstebanLorenzano.155] 21.0
Image: Pharo1.3 [Latest update: #13320]
UndefinedObject(Object)>>doesNotUnderstand: #wait
