Hi Paul, On 30 Dec 2011, at 04:57, Paul DeBruicker wrote:
I'm pretty sure I'm having the same problem Phillipe had/described in this message:
http://forum.world.st/Zinc-crashing-image-at-start-up-td3785797.html
At least the PharoDebug.log is the same. It happens on both the most recent Cog and interpreter VM.
I am sorry for your troubles. This is also related to http://code.google.com/p/pharo/issues/detail?id=4768 which is fixed in in 1.4 and in 1.3 #13314. If you are using 1.3 it is always a good idea to manually upgrade Zn to its latest version (the version is 1.3 is quite old). When using 'running' Zn servers based Seaside adaptors that need to survive image saves, I would advise using ZnManagingMultiThreadedServer like this: ZnZincServerAdaptor new port: 8080; serverClass: ZnManagingMultiThreadedServer; start Adaptors based on ZnManagingMultiThreadedServer will track and close all open worker connections and socket streams when needed.
Is there a way to recover from this?
I could follow Sean's instructions from this thread if necessary:
http://forum.world.st/Fwd-Oops-I-put-a-halt-in-a-startup-method-td3800729.ht...
Or is there a way to extract changes from a changes file for one image into another image? I'd rather fix the broken image but if its not possible I'd then just try to load those changes I don't have.
Thanks for any guidance you can provide.
I am no expert at reviving crashing images, maybe others can help. Regards, Sven