August 2014 - Pharo-dev - lists.pharo.org

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

by Eliot Miranda

On Thu, Jul 31, 2014 at 11:21 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Thu, Jul 31, 2014 at 10:53 PM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > >> >> >> >> >> *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part >> de* stepharo >> *EnvoyÃ© :* jeudi 31 juillet 2014 22:55 >> *Ã :* Pharo Development List >> *Objet :* Re: [Pharo-dev] Pharo image corruption and fatal VM error with >> Roassal >> >> >> >> vincent >> >> you can take an image/change copy >> your change as the change of the new image >> and do recovery last changes and you get all your changes back. >> >> Ok that is cool. But the things that I wrote in the Workspace, I canât >> get them back? >> > > try e.g. strings - foo.image | tr \\015 \\012 | grep. Or load the image > in the VM simulator and search. Or load the image in gdb and search. > > they're in there somewhere. just takes some digging. > or have you tried starting up the image headless and searching using a filein? pharovm -headless myimage.image script.st where script.st does something along the lines of ByteString allInstancesDo: [:s| ('*foo*' match: s) ifTrue: [... -- Aloha, Eliot

Aug. 1, 2014

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

by Eliot Miranda

On Thu, Jul 31, 2014 at 10:53 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > > > > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* stepharo > *EnvoyÃ© :* jeudi 31 juillet 2014 22:55 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] Pharo image corruption and fatal VM error with > Roassal > > > > vincent > > you can take an image/change copy > your change as the change of the new image > and do recovery last changes and you get all your changes back. > > Ok that is cool. But the things that I wrote in the Workspace, I canât get > them back? > try e.g. strings - foo.image | tr \\015 \\012 | grep. Or load the image in the VM simulator and search. Or load the image in gdb and search. they're in there somewhere. just takes some digging. > Vincent > > ------------------------------ > > 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. > -- best, Eliot

Aug. 1, 2014

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

by Blondeau Vincent

De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de stepharo EnvoyÃ© : jeudi 31 juillet 2014 22:55 Ã : Pharo Development List Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal vincent you can take an image/change copy your change as the change of the new image and do recovery last changes and you get all your changes back. Ok that is cool. But the things that I wrote in the Workspace, I can't get them back? Vincent ________________________________ 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.

Aug. 1, 2014

[pharo-project/pharo-core] 785095: 40148

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 78509505e1b59550db96856d564034e7b5659e3b https://github.com/pharo-project/pharo-core/commit/78509505e1b59550db96856d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-01 (Fri, 01 Aug 2014) Changed paths: M OpalDecompiler.package/OCDecompiler.class/instance/private/quickMethod.st M OpalDecompiler.package/OCDecompilerConstructor.class/instance/constructor/codeMethod_block_tempVars_primitive_class_.st A OpalDecompiler.package/OCDecompilerConstructor.class/instance/private/pragmasForMethod_.st M OpalDecompiler.package/extension/RBMessageNode/instance/toDoFromWhileWithInit_.st M OpalDecompiler.package/extension/RBMessageNode/instance/toDoLimit_.st M OpalDecompiler.package/extension/RBMethodNode/instance/primitiveErrorVariableName.st M OpalDecompiler.package/extension/RBMethodNode/instance/removeAndRenameLastTempIfErrorCode.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script148.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40148.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40148 13751 OpalDecompiler missdecompile named primitives https://pharo.fogbugz.com/f/cases/13751 13750 OpalDecompiler raises errors in rare cases when decompiling to:do: and to:by:do: https://pharo.fogbugz.com/f/cases/13750 http://files.pharo.org/image/40/40148.zip

Aug. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40148 Home: https://github.com/pharo-project/pharo-core

Aug. 1, 2014

Re: [Pharo-dev] where the...

by Norbert Hartl

Why you don't like it? Norbert > Am 01.08.2014 um 09:48 schrieb stepharo <stepharo(a)free.fr>: > > I can tell you that I do not like jenkins but we have it, it works and it is maintained. So I lobotomize myself when I use it and it looks ok :) > > Stef > >> On 1/8/14 01:36, Eliot Miranda wrote: >> *&^% do I find build artifacts for https://ci.inria.fr/pharo/job/Pharo-4.0/lastSuccessfulBuild/? There's no pointer to an image/changes combo I can see. >> -- >> Aloha, >> Eliot > >

Aug. 1, 2014

Re: [Pharo-dev] where the...

by Eliot Miranda

On Thu, Jul 31, 2014 at 9:48 PM, stepharo <stepharo(a)free.fr> wrote: > I can tell you that I do not like jenkins but we have it, it works and it > is maintained. So I lobotomize myself when I use it and it looks ok :) > I like it very much. But there's a lot of freedom to design the server and make it easier to find results, etc. For example at Cadence Bob Westergaard has put a lot of effort into our Jenkins server with tabs grouping different build tasks by VM, Newspeak, Spur, etc. So I find it easier to navigate than the Pharo one. In particular it would be great if thee were pointers to the latest build artifacts on https://ci.inria.fr/pharo/job/Pharo-4.0/. Is that possible? Stef > > On 1/8/14 01:36, Eliot Miranda wrote: > >> *&^% do I find build artifacts for https://ci.inria.fr/pharo/job/ >> Pharo-4.0/lastSuccessfulBuild/? There's no pointer to an image/changes >> combo I can see. >> -- >> Aloha, >> Eliot > > -- Aloha, Eliot

Aug. 1, 2014

Re: [Pharo-dev] where the...

by stepharo

I can tell you that I do not like jenkins but we have it, it works and it is maintained. So I lobotomize myself when I use it and it looks ok :) Stef On 1/8/14 01:36, Eliot Miranda wrote: > *&^% do I find build artifacts for > https://ci.inria.fr/pharo/job/Pharo-4.0/lastSuccessfulBuild/? There's > no pointer to an image/changes combo I can see. > -- > Aloha, > Eliot

Aug. 1, 2014

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

by stepharo

On 1/8/14 08:56, Ciprian Teodorov wrote: > > > On Jul 31, 2014 11:03 PM, "Nicolai Hess" <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>> wrote: > > > > Is is not that easy :) > > TRMorph already checks for a new session. > > TRCanvas not, but could be done the same way - maybe. It is > difficult as TRCanvas are shared by different objects. > > And it is more difficult for TRShape. > > > > I know Igors argument against a session management in Athens for > > recreating cairo resources on image start up. It is not the job of > Athens. > > Maybe session management should be implemented by the cairo binding > (or an abstraction on top of it, that is then used by athens). > It will when the system will be fully athens based. Now each client should handle it his way. > This way we don't clutter Athens with such low level stuff, and we > offer the user a high-level usable cairo binding, which can be also > used outside athens. > > Cheers, > Ciprian > > > > > But it is a bit different for resources created through Athens core api. > > How can the user (TRShape for example) know, that a path created by > > an Athens surface referes to an external resource? > > > > The attached changeset implements a simple check for TRCanvas and > > resets paths if the canvas changes. This solves the crash on > > image start up.But it is not a good solution. > > > > > > > > > > 2014-07-31 16:23 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com > <mailto:siguctua@gmail.com>>: > > > >> 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. > >> > > > > That's another story. The projects I have seen, using athens, do > this with an explicit use > > on AthensCairoSurface. Is there already a way to instantiate an > AthensSurface depending on the > > available libraries? And AthensBalloon and AthensCairo don't differ > only in rendering quality, so there > > is no real fallback option. > > > > > > > > > >> > >> > >> On 31 July 2014 16:09, Alexandre Bergel <alexandre.bergel(a)me.com > <mailto:alexandre.bergel@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 > <mailto: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(a)gmail.com > <mailto:usman.bhatti@gmail.com>>: > >>> > > >>> > > >>> > > >>> > On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent > <vincent.blondeau(a)worldline.com > <mailto: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 > <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 : > >>> > > >>> > <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 <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: > >>> > > >>> > <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 <mailto:Moose-dev@iam.unibe.ch> > >>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >>> > >>> -- > >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>> Alexandre Bergel http://www.bergel.eu > >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>> > >>> > >>> > >>> > >> > >> > >> > >> -- > >> Best regards, > >> Igor Stasenko. > > > > >

Aug. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40147 Home: https://github.com/pharo-project/pharo-core

Aug. 1, 2014