- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ESUG 2014 REMINDER: 11th Innovation Technology Awards

by HernÃ¡n Morales Durand

Thank you. Unfortunately I do not know somebody, but if some attendant likes bioinformatics I would gladly provide instructions. Otherwise maybe next ESUG :) Best regards, HernÃ¡n 2014-07-31 9:28 GMT-03:00 <jdelgado(a)lsi.upc.edu>: > Someone should present the submission and, eventually, get the prize at > the social event. If you know somebody who attends the conference and that > is able to answer questions about your software, that would do. > > Bests, > > Jordi > > > > Hi Jordi, > > > > Apologies if this was asked before. Does ESUG accept a presentation/demo > > without the coder being in presence in Cambridge, England? > > Cheers, > > > > HernÃ¡n > > > > > > > > 2014-07-27 4:15 GMT-03:00 <jdelgado(a)lsi.upc.edu>: > > > >> Hi guys, > >> > >> It's been sort of a tradition to do last minute submits to ESUG > >> Innovation > >> Technology Awards. Let's break with this tradition, ok? You can start > >> submitting your software now! :-) > >> > >> Thus: > >> > >> ESUG 2014 REMINDER: 11th Innovation Technology Awards > >> http://esug.org/Conferences/2014/Innovation-Technology-Awards > >> > >> Have you written innovative Smalltalk? The developers of any > >> Smalltalk-based software can enter by submitting a 3-5min video of their > >> software. Entrants demo their systems in a session at the end of Monday > >> August 18th 2014, after which the conference attendees vote. (A vote > >> consists in providing a sorted list of 3 preferred pieces of software.) > >> > >> The top 3 teams with the most innovative software will receive, > >> respectively, 500 Euros, 300 Euros and 200 Euros. The results are > >> announced in the Awards ceremony that is held during the social event. > >> > >> Applicants should provide the following information on the conference > >> registration server. Once you have registered your personal info, an > >> 'Awards' menu allows submitting your software. You can provide this > >> information when you first register, or login again later and update > >> your > >> details. The registration server will open soon. You can start preparing > >> your software right now though. > >> > >> Info to provide: > >> > >> Name of the software > >> Licence information (free, shareware, or commercial) > >> Name of the Smalltalk dialect used > >> Name, Affiliation and Country of developers > >> Besides, it would be great if the submission could include: > >> > >> URL for a video (3-5 min) showing a screencast / demo of the software > >> URL for downloading the software or at least a runnable demo > >> Deadline: August 15th > >> > >> Any Smalltalker can apply (students, companies, ...). The presented > >> piece > >> of code/software should be written in Smalltalk or directly support > >> Smalltalk (e.g. Smalltalk VM). All Smalltalk dialects are accepted. The > >> applicant should be "strongly related" to the presented code, be it as > >> an > >> author, as owner of the copyright/copyleft, or as an official > >> representative of the copyright/copyleft owner. > >> > >> Bests, > >> > >> Jordi > >> > >> > >> > >> > > > > > >

July 31, 2014

Re: [Pharo-dev] Android VM Status

by Alexandre Bergel

This is a fantastic news JB. Keep going!!! Alexandre On Jul 31, 2014, at 10:33 AM, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > Hi, > I made some advance on Android StackVM (using the standard unix sources). > > :-) > > Last Unix Stack VM with last 40Pharo image (a little bit modified cause au no-NativeBoost and some constraint from the Android Sandboxing ). > Content: > - Somes lines of code change in SqUnixMain.c (using if define android, but not a lot, just for allow to load external lib :-). > - 1 communication with java / C files, (will be split in two or three file one for printing debugging, one or two for core). > - 1 external graphical plugins. vm-display-android, really short but for android, because the rendering is done by Android. > > > All these plugins are includes (not deeply tested yet, but most of them should work): > AndroidPlugin (for now I just allow to do debug printing from the image in the logCat), BitBltPlugin, B2DPlugin, BMPReadWriterPlugin, CroquetPlugin, DSAPrims, FFTPlugin, FileCopyPlugin, FilePlugin, FloatArrayPlugin, FloatMathPlugin, JoystickTabletPlugin, JPEGReaderPlugin, LargeIntegers,Matrix2x3Plugin, RePlugin, SecurityPlugin, JPEGReadWriter2Plugin, SocketPlugin, MiscPrimitivePlugin, ZipPlugin. > > And a lot of debugging. :-). > > Next step: > - fixing all the Event. > - Do a real Configuration generator to be able to generate from Jenkins using the NDK. > - Then merge in the main PharoVM Git :-). > - Do a configuration to allow older pharo image to run on it. Maybe older but I not convince yet. > - And obviously a job for allow anybody to create a android package with it's own image :-) > > See you soon :-) > > <IMG_3934.jpeg> > > Best Regards > Dr Arnaud > jbaptiste.arnaud(a)gmail.com > > > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 31, 2014

Re: [Pharo-dev] Should nested mutexes work in Pharo 3.0?

by ClÃ©ment Bera

2014-07-31 14:53 GMT+02:00 Levente Uzonyi <leves(a)elte.hu>: > On Thu, 31 Jul 2014, Jan Vrany wrote: > > On 31/07/14 10:45, Marcel Taeumel wrote: >> >>> Hi! :) >>> >>> I am playing around with Animations [1] in the Moose 5.0/Pharo 3.0 image >>> [2]. Nested use of the same mutex seems to freeze the image. Should that >>> work? >>> >> >> No, it should not :-) Use Monitor instead. >> > > Then what's the difference between Semaphore and Mutex in Pharo? Mutex are reentrant, Semaphore are not. > > > > Levente > > > >> Jan >> >> >>> Best, >>> Marcel >>> >>> [1] https://github.com/marceltaeumel/animations >>> [2] >>> https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/ >>> artifact/moose-5.0.zip >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Should- >>> nested-mutexes-work-in-Pharo-3-0-tp4771110.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >> >> >> >

July 31, 2014

Re: [Pharo-dev] Android VM Status

by Benjamin

Good job! ;) Ben On 31 Jul 2014, at 16:33, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > Hi, > I made some advance on Android StackVM (using the standard unix sources). > > :-) > > Last Unix Stack VM with last 40Pharo image (a little bit modified cause au no-NativeBoost and some constraint from the Android Sandboxing ). > Content: > - Somes lines of code change in SqUnixMain.c (using if define android, but not a lot, just for allow to load external lib :-). > - 1 communication with java / C files, (will be split in two or three file one for printing debugging, one or two for core). > - 1 external graphical plugins. vm-display-android, really short but for android, because the rendering is done by Android. > > > All these plugins are includes (not deeply tested yet, but most of them should work): > AndroidPlugin (for now I just allow to do debug printing from the image in the logCat), BitBltPlugin, B2DPlugin, BMPReadWriterPlugin, CroquetPlugin, DSAPrims, FFTPlugin, FileCopyPlugin, FilePlugin, FloatArrayPlugin, FloatMathPlugin, JoystickTabletPlugin, JPEGReaderPlugin, LargeIntegers,Matrix2x3Plugin, RePlugin, SecurityPlugin, JPEGReadWriter2Plugin, SocketPlugin, MiscPrimitivePlugin, ZipPlugin. > > And a lot of debugging. :-). > > Next step: > - fixing all the Event. > - Do a real Configuration generator to be able to generate from Jenkins using the NDK. > - Then merge in the main PharoVM Git :-). > - Do a configuration to allow older pharo image to run on it. Maybe older but I not convince yet. > - And obviously a job for allow anybody to create a android package with it's own image :-) > > See you soon :-) > > <IMG_3934.jpeg> > > Best Regards > Dr Arnaud > jbaptiste.arnaud(a)gmail.com > > > > > > > >

July 31, 2014

Android VM Status

by Jean Baptiste Arnaud

Hi, I made some advance on Android StackVM (using the standard unix sources). :-) Last Unix Stack VM with last 40Pharo image (a little bit modified cause au no-NativeBoost and some constraint from the Android Sandboxing ). Content: - Somes lines of code change in SqUnixMain.c (using if define android, but not a lot, just for allow to load external lib :-). - 1 communication with java / C files, (will be split in two or three file one for printing debugging, one or two for core). - 1 external graphical plugins. vm-display-android, really short but for android, because the rendering is done by Android. All these plugins are includes (not deeply tested yet, but most of them should work): AndroidPlugin (for now I just allow to do debug printing from the image in the logCat), BitBltPlugin, B2DPlugin, BMPReadWriterPlugin, CroquetPlugin, DSAPrims, FFTPlugin, FileCopyPlugin, FilePlugin, FloatArrayPlugin, FloatMathPlugin, JoystickTabletPlugin, JPEGReaderPlugin, LargeIntegers,Matrix2x3Plugin, RePlugin, SecurityPlugin, JPEGReadWriter2Plugin, SocketPlugin, MiscPrimitivePlugin, ZipPlugin. And a lot of debugging. :-). Next step: - fixing all the Event. - Do a real Configuration generator to be able to generate from Jenkins using the NDK. - Then merge in the main PharoVM Git :-). - Do a configuration to allow older pharo image to run on it. Maybe older but I not convince yet. - And obviously a job for allow anybody to create a android package with it's own image :-) See you soon :-) Best Regards Dr Arnaud jbaptiste.arnaud(a)gmail.com

July 31, 2014

Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error with Roassal

by Jean Baptiste Arnaud

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 On 31 Jul 2014, at 16:09, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 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(a)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(a)gmail.com>: >> >> >> >> On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent <vincent.blondeau(a)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(a)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(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > Best Regards Dr Arnaud jbaptiste.arnaud(a)gmail.com

July 31, 2014

Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error with Roassal

by Igor Stasenko

The recipe is simple: isolate the code in your application in a way that if certain feature not available (line nativeboost), it won't put your image into endless exception throwing loop. On 31 July 2014 16:09, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 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(a)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(a)gmail.com>: > > > > > > > > On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent < > vincent.blondeau(a)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(a)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(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- Best regards, Igor Stasenko.

July 31, 2014

Re: [Pharo-dev] Should nested mutexes work in Pharo 3.0?

by Sebastian Sastre

On Jul 31, 2014, at 6:55 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: >> >> I am playing around with Animations [1] in the Moose 5.0/Pharo 3.0 image >> [2]. Nested use of the same mutex seems to freeze the image. Should that >> work? > > No, it should not :-) Use Monitor instead. +1 nested mutexes should not work not in pharo nor anything else Monitors are for reentering stuff

July 31, 2014

Re: [Pharo-dev] Should nested mutexes work in Pharo 3.0?

by Marcel Taeumel

Ah, okay. Just stumpled upon this part of the POSIX specification [1] and thought there could be this recursive property in mutexes for Pharo, too. :) Guess I have to use semaphores then. Best, Marcel [1] http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_mutexattr_… -- View this message in context: http://forum.world.st/Should-nested-mutexes-work-in-Pharo-3-0-tp4771110p477… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 31, 2014

Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error with Roassal

by Alexandre Bergel

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(a)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(a)gmail.com>: > > > > On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent <vincent.blondeau(a)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(a)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(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 31, 2014