Pharo on Windows Issue
Locked
Pharo on Windows Issue
 
|
Hi Janko,
This is not a big deal, and it's not anything new either. The screenshot is from a fresh Pharo 1.4 image on Windows after loading Aida 6.4. After a few minutes a #messageNotUnderstood message pops up.
Basically whenever out-of-the-box Aida runs some periodic task it calls ExternalWindowsOSProcess#value on Pharo for Windows (v 1.3 and 1.4), and it fails here (see the part in red): | procInfo mainThread | self isNotYetRunning ifTrue: [procInfo := OSProcess accessor primCommand: self commandLine.
procInfo isNil ifTrue: [self initialStdErr nextPutAll: 'cannot execute ', self commandLine; cr.
self exitStatus: #cannotExecuteCommandLine. "FIXME: Close the OSPipes now, otherwise the image will block on a read"
self closeStreams. [self complete] fork "defer execution so OSPipes stay in place for now"]
Apparently the call to self#initialStdErr fails to return an object and nextPutAll is sent to a Nil object, which doesn't understand that selector. In general the code in that method looks dodgy (several "FIXME" comments) but I'm not clear if its Aida code or Pharo code... looks like a Pharo problem but I gather it is a good idea to report it here since Aida is affected by it on Pharo for Windows.
- Bob
_______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
PharoOnWindowsIssue.png (187K)
Re: Pharo on Windows Issue
|
|
Re: Pharo on Windows Issue
Administrator
|
In reply to this post by bobcalco
I noticed the same.
|
Re: Pharo on Windows Issue
|
|
| Free forum by Nabble | Edit this page |