Segmentation fault on Moose 6.1 Build

I fixed the Pharo image used to the 60418 to get a working moose image since the bug with Athens is resolved.

Cheers,
Vincent

> -----Message d'origine-----
> De : Moose-dev [mailto:[hidden email]] De la part de
> Tudor Girba
> Envoyé : jeudi 2 mars 2017 16:42
> À : Pharo Development List
> Cc : Moose-related development
> Objet : [Moose-dev] Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1

> Build
>
> Hmm, it looks like something changed and the build is now yellow.
>
> Does anyone have the time to check this mysterious behavior?
>
> Cheers,
> Doru
>
>
> > On Mar 2, 2017, at 1:24 PM, Pavel Krivanek <[hidden email]>
> wrote:
> >
> > I will try to make some easier way to reproduce it and open an issue
> >
> > -- Pavel
> >
> > 2017-03-02 11:58 GMT+01:00 Pavel Krivanek <[hidden email]>:
> > Hm, I haven't check the time of the failing build... Yes, it will be related...
> >
> > 2017-03-02 11:51 GMT+01:00 Tudor Girba <[hidden email]>:
> > Except for tiny changes in Athens in 60419 :)
> >
> > Doru
> >
> >
> > > On Mar 2, 2017, at 11:33 AM, Pavel Krivanek
> <[hidden email]> wrote:
> > >
> > > On image side nothing relevant happened in 60418 where it started to
> fail.
> > >
> > > -- Pavel
> > >
> > > 2017-03-02 11:31 GMT+01:00 Blondeau Vincent
> <[hidden email]>:
> > > I heard that the gc compactor have changed.
> > >
> > > Cheers,
> > > Vincent
> > >
> > > > -----Message d'origine-----
> > > > De : Moose-dev [mailto:[hidden email]] De la
> > > > part de Tudor Girba Envoyé : jeudi 2 mars 2017 11:29 À : Pharo
> > > > Development List Cc : Moose-related development Objet :
> > > > [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build
> > > >
> > > > Hi,
> > > >
> > > > Was there a change related to the stable VM?
> > > >
> > > > Cheers,
> > > > Doru
> > > >
> > > >
> > > > > On Mar 2, 2017, at 11:23 AM, Blondeau Vincent
> > > > <[hidden email]> 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?
> > > > >
> > > > > Thanks in advance,
> > > > >
> > > > > Cheers,
> > > > > 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.!!!"
> > > > > <dump.txt>
> > > >
> > > > --
> > > > www.tudorgirba.com
> > > > www.feenk.com
> > > >
> > > > “Live like you mean it."
> > > >
> > > > _______________________________________________
> > > > Moose-dev mailing list
> > > > [hidden email]
> > > > 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.!!!"
> > >
> >
> > --
> > www.tudorgirba.com
> > www.feenk.com
> >
> > "Yesterday is a fact.
> >  Tomorrow is a possibility.
> >  Today is a challenge."
> >
> >
> >
> >
> >
> >
> >
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Beauty is where we see it."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> 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.!!!"

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?

 

Thanks in advance,

 

Cheers,

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.!!!"

 

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 <[hidden email]> 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?

 

Thanks in advance,

 

Cheers,

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

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:[hidden email]] 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 <[hidden email]>
> wrote:
> >
> > Esteban created a working fix for this issue.
> >
> > Cheers,
> > -- Pavel
> >
> > <a href="tel:2017-03-03%203" value="+420201703033">2017-03-03 3:16 GMT+01:00 Ben Coman <[hidden email]>:
> > 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 <[hidden email]>
> >     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
> <[hidden email]> 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:[hidden email]] 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
> > > <[hidden email]> 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
> [hidden email]
> 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.!!!"

The integration took a wrong slice...

2017-03-03 10:34 GMT+01:00 Blondeau Vincent <[hidden email]>:

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:[hidden email]] 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 <[hidden email]>
> wrote:
> >
> > Esteban created a working fix for this issue.
> >
> > Cheers,
> > -- Pavel
> >
> > <a href="tel:2017-03-03%203" value="+420201703033" target="_blank">2017-03-03 3:16 GMT+01:00 Ben Coman <[hidden email]>:
> > 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 <[hidden email]>
> >     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
> <[hidden email]> 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:[hidden email]] 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
> > > <[hidden email]> 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
> [hidden email]
> 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.!!!"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev

The build is now green.

Did anyone else encounter problems with the new code when playing with Roassal?

Cheers,
Doru

> On Mar 3, 2017, at 11:39 AM, Pavel Krivanek <[hidden email]> wrote:
>
> The integration took a wrong slice...
>
> 2017-03-03 10:34 GMT+01:00 Blondeau Vincent <[hidden email]>:
> 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:[hidden email]] 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 <[hidden email]>
> > wrote:
> > >
> > > Esteban created a working fix for this issue.
> > >
> > > Cheers,
> > > -- Pavel
> > >
> > > 2017-03-03 3:16 GMT+01:00 Ben Coman <[hidden email]>:
> > > 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 <[hidden email]>
> > >     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
> > <[hidden email]> 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:[hidden email]] 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
> > > > <[hidden email]> 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
> > [hidden email]
> > 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.!!!"
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev