- Pharo-dev - lists.pharo.org

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

by Jan Vrany

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. Jan > > Best, > Marcel > > [1] https://github.com/marceltaeumel/animations > [2] > https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… > > > > -- > 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

Should nested mutexes work in Pharo 3.0?

by Marcel Taeumel

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? Best, Marcel [1] https://github.com/marceltaeumel/animations [2] https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… -- 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] Pharo image corruption and fatal VM error with Roassal

by Blondeau Vincent

Yes it is. But I will not do TRMorph allInstances do: #delete In command line every dayâ¦ 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<mailto: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 : [cid:image001.png@01CFACAF.C4370C70] 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<http://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: [cid:image002.png@01CFACAF.C4370C70] 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.

July 31, 2014

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

by Blondeau Vincent

The Eliot VM doesn't comes with libCairo and Roassal doesn't work into. But it's helpful to reopen the image to retrieve the work done ! -----Message d'origine----- De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Hilaire EnvoyÃ© : jeudi 31 juillet 2014 10:54 Ã : pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal Looks like Cairo can't be loaded. Does the Eliot VM comes with libCairo? Hilaire Le 31/07/2014 16:50, Blondeau Vincent a Ã©crit : > 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 : > > 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: > > 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. -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu 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.

July 31, 2014

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

by Usman Bhatti

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 : > > 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: > > > > 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. >

July 31, 2014

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

by Hilaire

Looks like Cairo can't be loaded. Does the Eliot VM comes with libCairo? Hilaire Le 31/07/2014 16:50, Blondeau Vincent a Ã©crit : > 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 : > > 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: > > 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. -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

July 31, 2014

Pharo image corruption and fatal VM error with Roassal

by Blondeau Vincent

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 : [cid:image001.png@01CFACAA.E0CB2060] 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: [cid:image002.png@01CFACAD.350D7DB0] 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.

July 31, 2014

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

by HernÃ¡n Morales Durand

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

Fwd: World Skills 2015 Sao Paulo

by S Krish

I am not able to post to Pharo-users list.. Can anyone forward it. ---------- Forwarded message ---------- From: S Krish <krishnamachari.sudhakar(a)gmail.com> Date: Thu, Jul 31, 2014 at 11:59 AM Subject: World Skills 2015 Sao Paulo To: A friendly place where any question about pharo is welcome < pharo-users(a)lists.gforge.inria.fr> http://www.worldskills.org/index.php?option=com_content&task=view&id=1183&I… Nice place to showcase Pharo as emerging technology if 21 and lesser developers are coming up with projects on it..

July 31, 2014

Re: [Pharo-dev] [Pharo4] bench for browseAllSendersOf:

by stepharo

http://pharoweekly.wordpress.com/2014/07/31/pharo-tools-are-getting-faster/ On 29/7/14 09:28, Marcus Denker wrote: > Interesting... > > Pharo2: > [SystemNavigation new browseAllSendersOf: #+] bench '0.688 per second.â > > Pharo3: > [SystemNavigation new browseAllSendersOf: #+] bench '0.638 per second.' > > Pharo4: > [SystemNavigation new browseAllSendersOf: #+] bench '1.37 per second.' > > > And for Nautilus: > > Pharo2: > [Smalltalk tools browser open] bench '4.46 per second.' > > Pharo3: > [Smalltalk tools browser open] bench '6.77 per second.' > > Pharo4: > [Smalltalk tools browser open] bench '7.17 per second.â > > (all with the same VM) > > Marcus

July 31, 2014