- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Re: Re: Segmentation fault on Moose 6.1 Build

by Blondeau Vincent

Nice try, but it doesn't seems to :( : https://ci.inria.fr/moose/job/moose-6.1/556/console Smalltalk stack dump: 0xbfc61c50 I GrafPort>copyBits 0x9c1f7a8: a(n) GrafPort 0xbfc61c70 I GrafPort>image:at:sourceRect:rule: 0x9c1f7a8: a(n) GrafPort 0xbfc61ca0 I FormCanvas>image:at:sourceRect:rule: 0x9c12a98: a(n) FormCanvas Cheers, Vincent > -----Message d'origine----- > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > Tudor Girba > EnvoyÃ© : vendredi 3 mars 2017 10:22 > Ã : Pharo Development List > Cc : Moose-related development > Objet : [Moose-dev] Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1 > Build > > Thanks. > > I have switched the Moose job back to using the latest image. Letâs see how > it works. > > Cheers, > Doru > > > > On Mar 3, 2017, at 9:19 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > Esteban created a working fix for this issue. > > > > Cheers, > > -- Pavel > > > > 2017-03-03 3:16 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > > To confirm specific reproducibility, using... > > http://files.pharo.org/image/60/60421.zip > > > > I did... > > $ cd opensmalltalk-vm > > $ git checkout d54edc56 > > $ git log > > commit d54edc5638c9f90c80f214e59e19240f8ead87f8 > > Author: Eliot Miranda <eliot.miranda(a)gmail.com> > > Date: Thu Mar 2 09:53:05 2017 -0800 > > CogVM source as per VMMaker.oscog-eem.2143 > > Fix regression in Sista sources due to receiverTags work. > > > > $ cd build.linux32x86/pharo.cog.spur/build.debug > > $ cd products/debug/phcogspurlinuxht > > $ pharo ~/temp/Case19785/Pharo-60421.image > > > > World > Playground, evaluate... > > surf := AthensCairoSurface extent: Display extent. > > Display getCanvas drawImage: surf asForm at: 0@0 > > > > 70% ==> image seg fault > > 30% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > > > but doing > > Smalltalk snapshot: true andQuit: true. > > surf := AthensCairoSurface extent: Display extent. > > Display getCanvas drawImage: surf asForm at: 0@0. > > > > 100% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > > > > > Evaluate the following in Playground for 100% segfault from command line. > > > > EllipseMorph compile: 'step > > |surf| > > [ surf := AthensCairoSurface extent: Display extent. > > Display getCanvas drawImage: surf asForm at: 0@0. > > ] on: Error do: [ ]. > > self position: self position + (50@0). "To observe survival of seg > fault" '. > > Smalltalk snapshot: true andQuit: true. > > EllipseMorph new openInWorld. > > > > > > btw, I'm on 32-bit Debian 8 Jessie > > $ uname -a > > Linux dom0 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) > > i686 GNU/Linux > > > > cheers -ben > > > > > > On Fri, Mar 3, 2017 at 12:08 AM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > Hi Eliot, > > > > > > > > > > > > Thanks to take care of this issue! > > > > > > > > > > > > Pavel opened a bug issue here: > > > https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You > > > need the latest Pharo image and VM and it crashes under Linux > > > (32-bit) and OSX (El Captain, 32-bit VM). And I personally tried > > > with Windows7 and the bug happens too. > > > > > > > > > > > > To reproduce: Morph new testAthensRender > > > > > > > > > > > > An extract of the opened issue: > > > > > > > > > > > > Edited by Pavel Krivanek 02/03/2017 (Today) 16:10 > > > > > > An empty surface crashes it too: > > > surf := AthensCairoSurface extent: Display extent. > > > Display getCanvas drawImage: surf asForm at: 0@0 > > > > > > > > > > > > The problem is in the method AthensCairoSurface>>#asForm where the > > > previous slice started to add 1 to surface heigth > > > > > > > > > > > > Well, I tried to revert AthensCairoSurface>>#asForm which fixes this > > > particular case but Roassal still crashes on copyBits > > > > > > > > > > > > Cheers, > > > > > > Vincent > > > > > > > > > > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la > > > part de Eliot Miranda EnvoyÃ© : jeudi 2 mars 2017 17:03 Ã : Pharo > > > Development List Cc : Moose-related development; Squeak Virtual > > > Machine Development Discussion Objet : [Moose-dev] Re: [Pharo-dev] > > > Segmentation fault on Moose 6.1 Build > > > > > > Hi Vincent, > > > > > > first, apologies for the inconvenience, second, thanks! I badly > > > need reproducible failure cases to get the remaining bugs out of the > > > compactor and you have just provided me with one. Can you send me > > > the information I need to reproduce the build? What platforms does it > fall on? > > > > > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent > > > <vincent.blondeau(a)worldline.com> wrote: > > > > > > Hi, > > > > > > The latest builds of the Moose6.1 image are failing due to a > > > segmentation fault. > > > > > > Here is the link to the last build: > > > https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > > > How can we fix this? > > > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev !!!************************************************************************************* "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.!!!"

March 3, 2017

Re: [Pharo-dev] [Moose-dev] Re: Segmentation fault on Moose 6.1 Build

by Tudor Girba

Thanks. I have switched the Moose job back to using the latest image. Letâs see how it works. Cheers, Doru > On Mar 3, 2017, at 9:19 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Esteban created a working fix for this issue. > > Cheers, > -- Pavel > > 2017-03-03 3:16 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > To confirm specific reproducibility, using... > http://files.pharo.org/image/60/60421.zip > > I did... > $ cd opensmalltalk-vm > $ git checkout d54edc56 > $ git log > commit d54edc5638c9f90c80f214e59e19240f8ead87f8 > Author: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: Thu Mar 2 09:53:05 2017 -0800 > CogVM source as per VMMaker.oscog-eem.2143 > Fix regression in Sista sources due to receiverTags work. > > $ cd build.linux32x86/pharo.cog.spur/build.debug > $ cd products/debug/phcogspurlinuxht > $ pharo ~/temp/Case19785/Pharo-60421.image > > World > Playground, evaluate... > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0 > > 70% ==> image seg fault > 30% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > but doing > Smalltalk snapshot: true andQuit: true. > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0. > > 100% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > > Evaluate the following in Playground for 100% segfault from command line. > > EllipseMorph compile: 'step > |surf| > [ surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0. > ] on: Error do: [ ]. > self position: self position + (50@0). "To observe survival of seg fault" '. > Smalltalk snapshot: true andQuit: true. > EllipseMorph new openInWorld. > > > btw, I'm on 32-bit Debian 8 Jessie > $ uname -a > Linux dom0 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux > > cheers -ben > > > On Fri, Mar 3, 2017 at 12:08 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi Eliot, > > > > > > > > Thanks to take care of this issue! > > > > > > > > Pavel opened a bug issue here: > > https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You need the > > latest Pharo image and VM and it crashes under Linux (32-bit) and OSX (El > > Captain, 32-bit VM). And I personally tried with Windows7 and the bug > > happens too. > > > > > > > > To reproduce: Morph new testAthensRender > > > > > > > > An extract of the opened issue: > > > > > > > > Edited by Pavel Krivanek 02/03/2017 (Today) 16:10 > > > > An empty surface crashes it too: > > surf := AthensCairoSurface extent: Display extent. > > Display getCanvas drawImage: surf asForm at: 0@0 > > > > > > > > The problem is in the method AthensCairoSurface>>#asForm where the previous > > slice started to add 1 to surface heigth > > > > > > > > Well, I tried to revert AthensCairoSurface>>#asForm which fixes this > > particular case but Roassal still crashes on copyBits > > > > > > > > Cheers, > > > > Vincent > > > > > > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > > Eliot Miranda > > EnvoyÃ© : jeudi 2 mars 2017 17:03 > > Ã : Pharo Development List > > Cc : Moose-related development; Squeak Virtual Machine Development > > Discussion > > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build > > > > Hi Vincent, > > > > first, apologies for the inconvenience, second, thanks! I badly need > > reproducible failure cases to get the remaining bugs out of the compactor > > and you have just provided me with one. Can you send me the information I > > need to reproduce the build? What platforms does it fall on? > > > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent > > <vincent.blondeau(a)worldline.com> wrote: > > > > Hi, > > > > The latest builds of the Moose6.1 image are failing due to a segmentation > > fault. > > > > Here is the link to the last build: > > https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > How can we fix this? > -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

March 3, 2017

Re: [Pharo-dev] Tools > Calypso

by Denis Kudriashov

Hi. I will add, but now dev version is a bit broken. So it will happen after week ( I will be at vacation). I created issue https://github.com/dionisiydk/Calypso/issues/47. And feel free to implement it :) 2017-03-03 8:01 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > hi Dennis, > > When installing Calypso from the Catalog, its a pain to > have to search the forums to lookup up to do... > #ClySystemBrowser asClass open. > > Could you add an entry under World > Tools? > > cheers -ben >

March 3, 2017

[pharo-project/pharo-core] d7ab23: 60422

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d7ab2392cd49b9dac3b765de8d753cda99cb5d11 https://github.com/pharo-project/pharo-core/commit/d7ab2392cd49b9dac3b765de… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-03 (Fri, 03 Mar 2017) Changed paths: M Athens-Cairo.package/AthensCairoSurface.class/instance/converting/asForm.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60421.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60422.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60421.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60422.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60422 19785 Athens crashes the VM https://pharo.fogbugz.com/f/cases/19785 http://files.pharo.org/image/60/60422.zip

March 3, 2017

[pharo-project/pharo-core]

by GitHub

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

March 3, 2017

[Pharo6] [Issue Tracker] Current Status

by Marcus Denker

Hi, The current status is: Issues Tagged Pharo6: 52 Overall: 598 In the sprint *TODAY* we will remove all the Pharo6 tags from Priority âWould be niceâ and âFix if Timeâ. Please check the issues and change the priority of needed: https://pharo.fogbugz.com/f/filters/1192/6-0-All

March 3, 2017

Re: [Pharo-dev] [Moose-dev] Re: Segmentation fault on Moose 6.1 Build

by Pavel Krivanek

Esteban created a working fix for this issue. Cheers, -- Pavel 2017-03-03 3:16 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > To confirm specific reproducibility, using... > http://files.pharo.org/image/60/60421.zip > > I did... > $ cd opensmalltalk-vm > $ git checkout d54edc56 > $ git log > commit d54edc5638c9f90c80f214e59e19240f8ead87f8 > Author: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: Thu Mar 2 09:53:05 2017 -0800 > CogVM source as per VMMaker.oscog-eem.2143 > Fix regression in Sista sources due to receiverTags work. > > $ cd build.linux32x86/pharo.cog.spur/build.debug > $ cd products/debug/phcogspurlinuxht > $ pharo ~/temp/Case19785/Pharo-60421.image > > World > Playground, evaluate... > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0 > > 70% ==> image seg fault > 30% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > but doing > Smalltalk snapshot: true andQuit: true. > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0. > > 100% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > > Evaluate the following in Playground for 100% segfault from command line. > > EllipseMorph compile: 'step > |surf| > [ surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0. > ] on: Error do: [ ]. > self position: self position + (50@0). "To observe survival of seg fault" > '. > Smalltalk snapshot: true andQuit: true. > EllipseMorph new openInWorld. > > > btw, I'm on 32-bit Debian 8 Jessie > $ uname -a > Linux dom0 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 > GNU/Linux > > cheers -ben > > > On Fri, Mar 3, 2017 at 12:08 AM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > > Hi Eliot, > > > > > > > > Thanks to take care of this issue! > > > > > > > > Pavel opened a bug issue here: > > https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You > need the > > latest Pharo image and VM and it crashes under Linux (32-bit) and OSX (El > > Captain, 32-bit VM). And I personally tried with Windows7 and the bug > > happens too. > > > > > > > > To reproduce: Morph new testAthensRender > > > > > > > > An extract of the opened issue: > > > > > > > > Edited by Pavel Krivanek 02/03/2017 (Today) 16:10 > > > > An empty surface crashes it too: > > surf := AthensCairoSurface extent: Display extent. > > Display getCanvas drawImage: surf asForm at: 0@0 > > > > > > > > The problem is in the method AthensCairoSurface>>#asForm where the > previous > > slice started to add 1 to surface heigth > > > > > > > > Well, I tried to revert AthensCairoSurface>>#asForm which fixes this > > particular case but Roassal still crashes on copyBits > > > > > > > > Cheers, > > > > Vincent > > > > > > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part > de > > Eliot Miranda > > EnvoyÃ© : jeudi 2 mars 2017 17:03 > > Ã : Pharo Development List > > Cc : Moose-related development; Squeak Virtual Machine Development > > Discussion > > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build > > > > Hi Vincent, > > > > first, apologies for the inconvenience, second, thanks! I badly need > > reproducible failure cases to get the remaining bugs out of the compactor > > and you have just provided me with one. Can you send me the information > I > > need to reproduce the build? What platforms does it fall on? > > > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent > > <vincent.blondeau(a)worldline.com> wrote: > > > > Hi, > > > > The latest builds of the Moose6.1 image are failing due to a segmentation > > fault. > > > > Here is the link to the last build: > > https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > How can we fix this? >

March 3, 2017

Tools > Calypso

by Ben Coman

hi Dennis, When installing Calypso from the Catalog, its a pain to have to search the forums to lookup up to do... #ClySystemBrowser asClass open. Could you add an entry under World > Tools? cheers -ben

March 3, 2017

Spotter - could ignore message parameters

by Ben Coman

Just a quick note... I find that I often copy a long keyword message like this... dispatchEvent: anEvent with: from source code and paste it into spotter. But Spotter gets confused by the "anEvent" parameter, and even spaces, so I have to edit all those out. It would be cool if Spotter was smart enough to ignore any characters that don't parse as part of message syntax. also btw, is there a keyboard shortcut to open Spotter on selected text much like we do for Senders and Implementors? cheers -ben

March 3, 2017

Re: [Pharo-dev] Epicea - showing latest lost changes

by Ben Coman

On Tue, Feb 28, 2017 at 7:04 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Uko: OK, added it as: https://pharo.fogbugz.com/ > f/cases/19768/Epicea-Lost-Changes-Detector-Add-Apply-all- > button-on-top-of-the-list-of-change > > Stef: I see... each line should have a checkbox. I remember to see in > Spec's FastTableModel a method to enable that... I will try. > > Ben: I think that's not necessary because the EpLostChangesDetector > already opens a browser where only the "lost changes" are visible. Where > "lost changes" means everything logged by Epicea after last Image Save. > I paid particular attention this time to starting after a crash and one thing I'm uncertain about. Its good that the window says "Lost Changes Detected" but its not clear the meaning at the bottom where it says "22 filtered entries" Does this mean these 22 entries were not lost? Or is it some other reason? Also, I've a (only mild) concern that I can't see what these other entries are, since I don't know if they are important? Can you make it more explicit what the filter is? Oh, after a while I realise there is a tab for this. Perhaps at the bottom of the changes list you could say "22 filtered entries (see Active Filters tab)" to help slow people like me. So if 'remove all filters", what is the easy way to return to the identical previous "Lost Changes" filter. I realise now that I've been missing the old "indication of save points" Then I guess I'd be able to select that line and filter "afterwards" cheers -ben

March 3, 2017