Look like a very common Nativeboost error, if a external object is access without checking if we are on the same session (memory has changed so ...).
If it is that:
The clean solution:
- check the nativeboost session on external object accesses. Or at least the risky one. Should be done in the application that used NB.
Another solution to fixed a corrupted image:
- open with StackVM (no nativeboost).
- ugly but can save you: try to identify a suite of bytecode that is executed at launch use hex Editor and replace the first by return Self : 0x78, you should be able to reopend the image if a DNU pop DO NOT touch it :-)
- use Oz project to extract code
Extract your code and rebuild fresh image
Yes, and this is a mess.
I�ve spent quite some time in getting the session working with Roassal2 and it still does not work. I would appreciate help on this.
Alexandre
On Jul 31, 2014, at 8:58 AM, Nicolai Hess <nicolaihess@web.de> wrote:
It looks like Trachel does not recreate athens external resources.
There is an example in AthensSceneView, on how to check and reload
an AthensSurface.
2014-07-31 12:51 GMT+02:00 Usman Bhatti <usman.bhatti@gmail.com>:
On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent <vincent.blondeau@worldline.com> wrote:
Yes it is. But I will not do
TRMorph allInstances do: #delete
In command line every day�
It is only intended to recover your lost work in the image not for everyday use :).
Vincent
De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Usman Bhatti
Envoy� : jeudi 31 juillet 2014 10:59
� : Pharo Development List
Cc : Moose-related development
Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal
This may be related to this known issue reported a few days back.
https://code.google.com/p/moose-technology/issues/detail?id=1084
And there is a possible solution to recover your image.
usman
On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent <vincent.blondeau@worldline.com> wrote:
Hi,
Yesterday, I was using GraphET (a part of Roassal) to do some charts and, today, when I wanted to reopen the image.
And I got that :
<image001.png>
It is *very* unpleasant�
To reproduce the bug:
1 - You can do either:
| builder |
builder := GET2Line data: (0 to: 100) .
builder
y: [ :x | x*x ].
builder open.
Or
WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph should be opened.
2 - don�t close the graph and save the pharo image.
3 � Close the pharo image
4 - Reopen it
I am under W7 x64 with the latest moose image and the VM available on the pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july.
You will find the crash dump attached.
Thankfully, I managed to open the image with a latest VM (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip).
Thanks a lot Eliot ! :)
And I got this:
<image002.png>
Thanks in advance
Cheers,
Vincent BLONDEAU
Ce message et les pi�ces jointes sont confidentiels et r�serv�s � l'usage exclusif de ses destinataires. Il peut �galement �tre prot�g� par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm�diatement l'exp�diteur et de le d�truire. L'int�grit� du message ne pouvant �tre assur�e sur Internet, la responsabilit� de Worldline ne pourra �tre recherch�e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp�diteur ne donne aucune garantie � cet �gard et sa responsabilit� ne saurait �tre recherch�e pour tout dommage r�sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Ce message et les pi�ces jointes sont confidentiels et r�serv�s � l'usage exclusif de ses destinataires. Il peut �galement �tre prot�g� par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm�diatement l'exp�diteur et de le d�truire. L'int�grit� du message ne pouvant �tre assur�e sur Internet, la responsabilit� de Worldline ne pourra �tre recherch�e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp�diteur ne donne aucune garantie � cet �gard et sa responsabilit� ne saurait �tre recherch�e pour tout dommage r�sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.