Hi Sabine,

the vm from 29/09/2014 is not the last one. You can try this one:

http://files.pharo.org/vm/pharo/mac/stable-20150403.zip http://files.pharo.org/vm/pharo/mac/stable-20150403.zip

but… current Pharo VM is based in an old branch from Eliot sources, because in a moment I moved all development to a different branch for work on spur. While the spur branch should be able to produce regular Cog VMs, making a Pharo VM (with NB support) would be hard because I didn’t keep all NB related changes :( (this is because we realigned VM sources and it was a lot easier like that).

If you want a newer VM, and your code does not rely on any NB stuff, I suggest you try with latest Cog from Eliot site:

http://www.mirandabanda.org/files/Cog/VM/VM.r3397/ http://www.mirandabanda.org/files/Cog/VM/VM.r3397/

it should work without problems (but beware, some command line options can be different)

Please, keep us informed if you have any progression :)

cheers! Esteban

On 13 Jul 2015, at 18:34, Sabine Manaa manaa.sabine@gmail.com wrote:

Hi Eliot,

I downloaded the latest version from the Pharo website and the Pharo.exe has date 25.9.2014.

Is this not the most up-to-date Pharo VM? I had the problem also on my mac machine with the download of pharo 4.

I am trying to create a demo for reproducing but not yet successful. The problem is that the error seems to occur randomly. I start the image, work with my app and then after clicking a few times on the same button, it suddenly appears. Running exactly the same code!

I wonder why no one else has this problem with pharo 4.

I went back to pharo3 for production. Help would be great!

Regards Sabine

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

Hi Nicolai and Esteban,

will there be an official release for Pharo4 with a stable vm which does not include this bug? In this case I would wait and proceed with Pharo3 till then.

I don not do very special things and I wonder why I am the only person having this problem.

Btw I had the crashed Image problem, too. Another reason to go back to Pharo3 and wait.

Regards Sabine

2015-07-13 19:25 GMT+02:00 Nicolai Hess [via Smalltalk] < ml-node+s1294792n4837362h17@n4.nabble.com>:

2015-07-13 18:34 GMT+02:00 Sabine Manaa <[hidden email] http:///user/SendEmail.jtp?type=node&node=4837362&i=0>:

...

Hi Eliot,

I downloaded the latest version from the Pharo website and the Pharo.exe has date 25.9.2014.

Is this not the most up-to-date Pharo VM?

The most up-to-date pharo vm is from 09.07.15 (files.pharo.org/vm/pharo/ win|linux|mac/.../latest) or http://get.pharo.org/vmLatest50 this is the "latest" not the current "stable". But it works well.

...

I had the problem also on my mac machine with the download of pharo 4.

I am trying to create a demo for reproducing but not yet successful. The problem is that the error seems to occur randomly. I start the image, work with my app and then after clicking a few times on the same button, it suddenly appears. Running exactly the same code!

I wonder why no one else has this problem with pharo 4.

I went back to pharo3 for production. Help would be great!

Regards Sabine

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4836826&code=bWFuYWEuc2FiaW5lQGdtYWlsLmNvbXw0ODM2ODI2fC0xOTE3OTcxOTg5 . NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

Hi Esteban,

ok, I will try to find a reproducible case and try with the newer vm and come back to you!

Regards Sabine

2015-07-16 8:39 GMT+02:00 EstebanLM [via Smalltalk] < ml-node+s1294792n4837739h4@n4.nabble.com>:

Hi Sabine,

On 15 Jul 2015, at 17:43, Sabine Manaa <[hidden email] http:///user/SendEmail.jtp?type=node&node=4837739&i=0> wrote:

Hi Nicolai and Esteban,

will there be an official release for Pharo4 with a stable vm which does not include this bug?

We can release a new stable VM if we found it fixes the problem… but is hard for me to test it since I do not have a reproducible case :( Some feedback about the new VMs I suggested you to try would be cool, but I understand that doing experiments in production is not the best scenario possible :) In any case, if you can collect any other data, please keep us informed.

Esteban

In this case I would wait and proceed with Pharo3 till then.

I don not do very special things and I wonder why I am the only person having this problem.

Btw I had the crashed Image problem, too. Another reason to go back to Pharo3 and wait.

Regards Sabine

2015-07-13 19:25 GMT+02:00 Nicolai Hess [via Smalltalk] <<a href="x-msg://13/user/SendEmail.jtp?type=node&amp;node=4837689&amp;i=0" target="_top" rel="nofollow" link="external" class="">[hidden email]>:

...

2015-07-13 18:34 GMT+02:00 Sabine Manaa <[hidden email] http://user/SendEmail.jtp?type=node&node=4837362&i=0>:

...

Hi Eliot,

I downloaded the latest version from the Pharo website and the Pharo.exe has date 25.9.2014.

Is this not the most up-to-date Pharo VM?

The most up-to-date pharo vm is from 09.07.15 (files.pharo.org/vm/pharo/ win|linux|mac/.../latest) or http://get.pharo.org/vmLatest50 this is the "latest" not the current "stable". But it works well.

...

I had the problem also on my mac machine with the download of pharo 4.

I am trying to create a demo for reproducing but not yet successful. The problem is that the error seems to occur randomly. I start the image, work with my app and then after clicking a few times on the same button, it suddenly appears. Running exactly the same code!

I wonder why no one else has this problem with pharo 4.

I went back to pharo3 for production. Help would be great!

Regards Sabine

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here. NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

---

View this message in context: Re: pharo 4.0 Crashed in the VM thread again http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p4837689.html Sent from the Squeak VM mailing list archive http://forum.world.st/Squeak-VM-f104410.html at Nabble.com http://nabble.com/.

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4836826&code=bWFuYWEuc2FiaW5lQGdtYWlsLmNvbXw0ODM2ODI2fC0xOTE3OTcxOTg5 . NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

Hi Sabine,

you have a reproducible case. Does the image require any surrounding infrastructure to reproduce the problem or is it self-contained? Do you use any special Pharo facilities such as Native Boost? If the problem is self-contained would you be willing to try one of my recent VMs and see if it crashes there-on? If it does, I'd like either you to run the system using an assert-enabled VM and/or you to send me the image and changes and let me take a look at the crash. An assert-enabled VM is one full of run-time consistency checks and it tends to move the point of detection in a bug earlier, before things are so messed up that the VM actually crashes. It is significantly slower than the production VM, which is why its only used to debug/verify.

Ideally a reproducible case crashes from start-up without user intervention. This makes it more straight-forward to debug. If you can package the crash as a doit that starts with a snapshot that's ideal. Something like

Smalltalk image snapshot: true andQuit: true. self doSomethingThatCrashes

This can be run from inside an inspector on a live instance if necessary, avoiding needing to initialize the application, etc.

HTH

On Sun, Jul 19, 2015 at 5:59 AM, Sabine Manaa manaa.sabine@gmail.com wrote:

Hi Esteban,

I downloaded the Pharo vm with file date 16.7.2015 and startet it with a pharo 4 image (curl get.pharo.org/vmLatest50 | bash). The problem remains - also with the newer vm. I reproduced it twice, please see the stack dump below. Can you see in the dump below that I used the right vm? Is this helpful?

Now I try to create a reproducible case.

regards Sabine

---

Segmentation fault Sun Jul 19 14:45:32 2015

https://github.com/pharo-project/pharo-vm.git Commit: b292ce7c18d004482a2534c09000aa270583141f Date: 2015-06-15 16:45:13 +0200 By: Esteban Lorenzano estebanlm@gmail.com Jenkins build #14979

C stack backtrace: 0 Pharo 0x0004cb0f reportStackState + 159

Smalltalk stack dump: 0xbffc4b54 M Dictionary>at:ifAbsent: 0x23f5c340: a(n) Dictionary 0xbffc4b74 M RKACurrency class>currencyFor: 0x235ec820: a(n) RKACurrency class 0xbffc4b98 M RKAMoney class>amount:currencyCode: 0x235ea04c: a(n) RKAMoney class 0xbffc4bb8 M SmallInteger(Number)>eur 0x1=0 0xbffc4c28 M [] in INVALID RECEIVER>monthReportTripsTableData 0x2974394c: a(n) bad class 0xbffc4c54 I INVALID RECEIVER>do:with:when: 0x2974b558: a(n) bad class 0x2974b5c0 is not a context

Most recent primitives new: basicNew new: basicNew at:put: at:put: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew perform:with: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: basicNew basicNew indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: at:put: indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: new: at:put: at:put: at:put: basicNew basicNew basicNew new: basicNew new: basicNew new: basicNew new: basicNew at:put: at:put: basicNew **IncrementalGC**

    (Segmentation fault)

Segmentation fault Sun Jul 19 14:50:23 2015

https://github.com/pharo-project/pharo-vm.git Commit: b292ce7c18d004482a2534c09000aa270583141f Date: 2015-06-15 16:45:13 +0200 By: Esteban Lorenzano estebanlm@gmail.com Jenkins build #14979

C stack backtrace: 0 Pharo 0x0004cb0f reportStackState + 159

Smalltalk stack dump: 0xbffc6b10 M Array(OrderedCollection)>do: 0x24d390a0: a(n) Array 0xbffc6b30 M Array(Collection)>inject:into: 0x24d390a0: a(n) Array 0xbffc6ba4 M [] in INVALID RECEIVER>monthReportTripsTableData 0x24d30acc: a(n) bad class 0xbffc6bd0 I INVALID RECEIVER>do:with:when: 0x24d38790: a(n) bad class 0xbffc6bfc I INVALID RECEIVER>do:with: 0x24d38790: a(n) bad class 0xbffc6c24 I INVALID RECEIVER>datesDo: 0x24d38790: a(n) bad class 0xbffc6c60 I INVALID RECEIVER>monthReportTripsTableData 0x24d30acc: a(n) bad class 0x24d3864c is not a context

Most recent primitives basicNew new: basicNew new: basicNew at:put: at:put: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew perform:with: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: basicNew basicNew indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: at:put: indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: new: at:put: at:put: at:put: basicNew basicNew basicNew new: basicNew new: basicNew new: basicNew new: basicNew at:put: at:put: **IncrementalGC**

    (Segmentation fault)

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

Hi Sabine,

On Sun, Jul 19, 2015 at 11:13 PM, Sabine Manaa manaa.sabine@gmail.com wrote:

Hi Eliot,

I use MongoDB and the Problem occurs when the user clicks within its web browser. I don't use Native Boost etc. Only lots of Pharo features like Artifact, Zinc etc. Yes, sure, I can try with other vms. I can try to force the bug with a smalltalk script instead of clicking within the application but the need of mongo db remains. I will think about how to create a straight forward reproducible case to you. You can send the vm to me I will test it.

So the first step is simply to test with an up-to-date Cog VM and see if it still crashes. You can download them here:

http://www.mirandabanda.org/files/Cog/VM/VM.r3410

Are you on Mac OS X or Linux?

Regards

Sabine

2015-07-19 18:28 GMT+02:00 Eliot Miranda-2 [via Smalltalk] <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838285&i=0>:

...

Hi Sabine,

you have a reproducible case.  Does the image require any surrounding

infrastructure to reproduce the problem or is it self-contained? Do you use any special Pharo facilities such as Native Boost? If the problem is self-contained would you be willing to try one of my recent VMs and see if it crashes there-on? If it does, I'd like either you to run the system using an assert-enabled VM and/or you to send me the image and changes and let me take a look at the crash. An assert-enabled VM is one full of run-time consistency checks and it tends to move the point of detection in a bug earlier, before things are so messed up that the VM actually crashes. It is significantly slower than the production VM, which is why its only used to debug/verify.

Ideally a reproducible case crashes from start-up without user intervention. This makes it more straight-forward to debug. If you can package the crash as a doit that starts with a snapshot that's ideal. Something like

Smalltalk image snapshot: true andQuit: true.
self doSomethingThatCrashes

This can be run from inside an inspector on a live instance if necessary, avoiding needing to initialize the application, etc.

HTH

On Sun, Jul 19, 2015 at 5:59 AM, Sabine Manaa <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838214&i=0> wrote:

...

Hi Esteban,

I downloaded the Pharo vm with file date 16.7.2015 and startet it with a pharo 4 image (curl get.pharo.org/vmLatest50 | bash). The problem remains - also with the newer vm. I reproduced it twice, please see the stack dump below. Can you see in the dump below that I used the right vm? Is this helpful?

Now I try to create a reproducible case.

regards Sabine

---

Segmentation fault Sun Jul 19 14:45:32 2015

https://github.com/pharo-project/pharo-vm.git Commit: b292ce7c18d004482a2534c09000aa270583141f Date: 2015-06-15 16:45:13 +0200 By: Esteban Lorenzano <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838214&i=1> Jenkins build #14979

C stack backtrace: 0 Pharo 0x0004cb0f reportStackState + 159

Smalltalk stack dump: 0xbffc4b54 M Dictionary>at:ifAbsent: 0x23f5c340: a(n) Dictionary 0xbffc4b74 M RKACurrency class>currencyFor: 0x235ec820: a(n) RKACurrency class 0xbffc4b98 M RKAMoney class>amount:currencyCode: 0x235ea04c: a(n) RKAMoney class 0xbffc4bb8 M SmallInteger(Number)>eur 0x1=0 0xbffc4c28 M [] in INVALID RECEIVER>monthReportTripsTableData 0x2974394c: a(n) bad class 0xbffc4c54 I INVALID RECEIVER>do:with:when: 0x2974b558: a(n) bad class 0x2974b5c0 is not a context

Most recent primitives new: basicNew new: basicNew at:put: at:put: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew perform:with: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: basicNew basicNew indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: at:put: indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: new: at:put: at:put: at:put: basicNew basicNew basicNew new: basicNew new: basicNew new: basicNew new: basicNew at:put: at:put: basicNew **IncrementalGC**

    (Segmentation fault)

Segmentation fault Sun Jul 19 14:50:23 2015

https://github.com/pharo-project/pharo-vm.git Commit: b292ce7c18d004482a2534c09000aa270583141f Date: 2015-06-15 16:45:13 +0200 By: Esteban Lorenzano <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838214&i=2> Jenkins build #14979

C stack backtrace: 0 Pharo 0x0004cb0f reportStackState + 159

Smalltalk stack dump: 0xbffc6b10 M Array(OrderedCollection)>do: 0x24d390a0: a(n) Array 0xbffc6b30 M Array(Collection)>inject:into: 0x24d390a0: a(n) Array 0xbffc6ba4 M [] in INVALID RECEIVER>monthReportTripsTableData 0x24d30acc: a(n) bad class 0xbffc6bd0 I INVALID RECEIVER>do:with:when: 0x24d38790: a(n) bad class 0xbffc6bfc I INVALID RECEIVER>do:with: 0x24d38790: a(n) bad class 0xbffc6c24 I INVALID RECEIVER>datesDo: 0x24d38790: a(n) bad class 0xbffc6c60 I INVALID RECEIVER>monthReportTripsTableData 0x24d30acc: a(n) bad class 0x24d3864c is not a context

Most recent primitives basicNew new: basicNew new: basicNew at:put: at:put: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew perform:with: basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew basicNew basicNew basicNew perform:with: basicNew perform:with: basicNew basicNew basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew new: basicNew: basicNew basicNew: replaceFrom:to:with:startingAt: basicNew basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: basicNew: basicNew basicNew indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: at:put: indexOfAscii:inString:startingAt: basicNew: replaceFrom:to:with:startingAt: basicNew basicNew replaceFrom:to:with:startingAt: basicNew: replaceFrom:to:with:startingAt: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: stringHash:initialHash: basicNew at:put: new: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: at:put: stringHash:initialHash: basicNew at:put: new: at:put: at:put: at:put: basicNew basicNew basicNew new: basicNew new: basicNew new: basicNew new: basicNew at:put: at:put: **IncrementalGC**

    (Segmentation fault)

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

-- _,,,^..^,,,_ best, Eliot

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here . NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

---

View this message in context: Re: pharo 4.0 Crashed in the VM thread again http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p4838285.html Sent from the Squeak VM mailing list archive http://forum.world.st/Squeak-VM-f104410.html at Nabble.com.

This is production: Windows Server 2008 R2 Datacenter

Development is MacOs

2015-07-20 23:04 GMT+02:00 Stephan Eggermont [via Smalltalk] < ml-node+s1294792n4838441h66@n4.nabble.com>:

On 20/07/15 22:55, Eliot Miranda wrote:

...

Are you on Mac OS X or Linux?

Windows Server 2008 R2 Datacenter says the first mail in this thread

Stephan

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4836826&code=bWFuYWEuc2FiaW5lQGdtYWlsLmNvbXw0ODM2ODI2fC0xOTE3OTcxOTg5 . NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

Hi Sabine,

On Tue, Jul 21, 2015 at 12:27 AM, Sabine Manaa manaa.sabine@gmail.com wrote:

Eliot, is Cog.app-15.28.3410.tgz http://www.mirandabanda.org/files/Cog/VM/VM.r3410/Cog.app-15.28.3410.tgz the right one?

That's Mac OS X. You'll want cogwin-15.28.3410.zip

Regards Sabine

2015-07-21 9:24 GMT+02:00 Sabine Manaa <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838481&i=0>:

...

This is production: Windows Server 2008 R2 Datacenter

Development is MacOs

2015-07-20 23:04 GMT+02:00 Stephan Eggermont [via Smalltalk] <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838481&i=1>:

...

On 20/07/15 22:55, Eliot Miranda wrote:

...

Are you on Mac OS X or Linux?

Windows Server 2008 R2 Datacenter says the first mail in this thread

Stephan

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here. NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

---

View this message in context: Re: pharo 4.0 Crashed in the VM thread again http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p4838481.html Sent from the Squeak VM mailing list archive http://forum.world.st/Squeak-VM-f104410.html at Nabble.com.

Hi Eliot,

me again. I develop with Mac and production is Windows. The problem is independent from the OS.

Please see my post from Jul 21, 2015; 11:21am.

Do you want to send me the assert-enabled VM now?

Regards Sabine

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.

Hi,

with the help of Eliot, I was able to reduce the problem and created a fileout, it is only one class with one method. The fileout reproduces the crash. Take a new Pharo 4 image, file in the attached .st and do the steps described in the comment.

Eliot told me that it is possibly a compiler bug and asked me to send this to Marcus or Esteban. Here it is.

_Note_, that the method does not make sense because I removed all my stuff for creating an easy reproducible case. The crash dump looks similar to the dumps in my case, so I hope it is the same.

Eliots words are that " that the method should have the large context flag set but that it doesn't"

The key point is, as far as I understand, that the method is (too) long. My method also was long (it gathered much stuff for a big report.). After refactoring, it disapeared.

The punishment for writing a long method was hard, because it took a lot of time to find the reason for the crashes ;-)))

Have a nice sunday Sabine

2015-07-22 22:49 GMT+02:00 Eliot Miranda-2 [via Smalltalk] < ml-node+s1294792n4838728h63@n4.nabble.com>:

Hi Sabine,

On Tue, Jul 21, 2015 at 12:27 AM, Sabine Manaa <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838728&i=0> wrote:

...

Eliot, is Cog.app-15.28.3410.tgz http://www.mirandabanda.org/files/Cog/VM/VM.r3410/Cog.app-15.28.3410.tgz the right one?

That's Mac OS X. You'll want cogwin-15.28.3410.zip

...

Regards Sabine

2015-07-21 9:24 GMT+02:00 Sabine Manaa <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838481&i=0>:

...

This is production: Windows Server 2008 R2 Datacenter

Development is MacOs

2015-07-20 23:04 GMT+02:00 Stephan Eggermont [via Smalltalk] <[hidden email] http:///user/SendEmail.jtp?type=node&node=4838481&i=1>:

...

On 20/07/15 22:55, Eliot Miranda wrote:

...

Are you on Mac OS X or Linux?

Windows Server 2008 R2 Datacenter says the first mail in this thread

Stephan

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here. NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

---

View this message in context: Re: pharo 4.0 Crashed in the VM thread again http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p4838481.html Sent from the Squeak VM mailing list archive http://forum.world.st/Squeak-VM-f104410.html at Nabble.com.

-- _,,,^..^,,,_ best, Eliot

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4836826&code=bWFuYWEuc2FiaW5lQGdtYWlsLmNvbXw0ODM2ODI2fC0xOTE3OTcxOTg5 . NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

RKADemoCrash.st (9K) http://forum.world.st/attachment/4841825/0/RKADemoCrash.st

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p484... Sent from the Squeak VM mailing list archive at Nabble.com.

Pharo or Squeak ?

In squeak, this stackframe / large stackframe bug was introduced some months ago by a change for the compiler but it is already fixed. In pharo, we have a simliar bug (in pharos compiler (opal), not related to the change on the squeak compiler). This is a bug that is known but not yet fixed 13854 https://pharo.fogbugz.com/default.asp?13854 frameSize calculated wrongly for #lineSegmentsDo: !

2015-08-09 18:39 GMT+02:00 tim Rowledge tim@rowledge.org:

Sabine, As a general rule of thumb, if a method is too long to see at a glance - in practice this means too long to fit on your screen - then it almost certainly needs splitting up. I have been forcibly reminded of this a lot recently due to having to decode insanely long Python routines; seriously - 1100 lines for a single function?

tim

tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: FSRA: Forms Skip and Run-Away

Hi Eliot,

I tried with Cog.app-15.28.3410.tgz http://www.mirandabanda.org/files/Cog/VM/VM.r3410/Cog.app-15.28.3410.tgz and a new pharo4 image and changes file - and the problem remains, see dump below. I reproduced it twice.

Also, I was not able to open a browser but it worked also without, I used a script for initialization of my application.

The dump is short, it is not a copy and paste error.

I am asking myself if there is a problem in MY code but independly from the code - pharo should not crash - or? Is it possible that I do something wrong? I don't want to create time consuming create confusion based on my errors!

Could it be that there is a problem with the garbage collection? Because if I take an image with all my stuff loaded in the pharo4 vm and start it with cog vm above, I get this dump:

... Smalltalk stack dump: 0xbff6eb58 M INVALID RECEIVER>do: 0x125b63b4: a(n) bad class 0xbff6eb78 M INVALID RECEIVER>grow 0x125b6254 is in old space 0xbff6eb90 M INVALID RECEIVER>fullCheck 0x125b6254 is in old space 0xbff6eba8 M INVALID RECEIVER>atNewIndex:put: 0x125b6254 is in old space 0xbff6ebd0 M INVALID RECEIVER>at:put: 0x125b6254 is in old space 0xbff6ec44 M [] in INVALID RECEIVER>monthReportTripsTableData 0x125ad1bc is in old space 0xbff6ec70 I INVALID RECEIVER>do:with:when: 0x125b4db0: a(n) 0xbff6ec9c I INVALID RECEIVER>do:with: 0x125b4db0: a(n) 0xbff6ecc4 I INVALID RECEIVER>datesDo: 0x125b4db0: a(n) 0xbff6ed00 I INVALID RECEIVER>monthReportTripsTableData 0x125ad1bc is in old space 0xbff6ed24 I INVALID RECEIVER>addMonthReportTripsTable 0x125ad1bc is in old space 0xbff6ed44 I INVALID RECEIVER>createMonthReport: 0x125ad1bc is in old space 0xbff6ed70 I [] in INVALID RECEIVER>renderContentOn: 0x125ab250: a(n) bad class ...

Regards Sabine

################################### Segmentation fault Tue Jul 21 11:05:06 2015

/Users/sabine/Desktop/Cog.app/Contents/MacOS/Squeak Squeak VM version: 4.5 4.0.3410 Mac OS X built on Jul 19 2015 04:40:14 UTC Compiler: 4.2.1 (Apple Inc. build 5666) (dot 3) [Production VM] Built from: CoInterpreter VMMaker.oscog-eem.1426 uuid: 94ab92ba-c5c4-4953-8566-a4cd9c38df1f Jul 19 2015 With: StackToRegisterMappingCogit VMMaker.oscog-eem.1427 uuid: c5cb18c5-f69e-4e41-8f87-943a495659b4 Jul 19 2015 Revision: VM: r3410 http://www.squeakvm.org/svn/squeak/branches/Cog Date: 2015-07-18 19:15:20 -0700 Plugins: r3405 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins

C stack backtrace & registers: eax 0x00000016 ebx 0x0d8526d4 ecx 0x133ce35f edx 0x0d63a5b8 edi 0x0d852678 esi 0x0d852678 ebp 0xbff5cc18 esp 0xbff5cbd0 eip 0x000e1535 (0 Squeak 0x000e1535 mapPointersInObjectsFromto + 1461)

Smalltalk stack dump: 0xbff9eba8 M Array(OrderedCollection)>do: 0xd65b13c: a(n) Array 0xbff9ebc8 M Array(Collection)>inject:into: 0xd65b13c: a(n) Array 0xbff9ec3c M [] in Segmentation fault Tue Jul 21 11:07:54 2015

/Users/sabine/Desktop/Cog.app/Contents/MacOS/Squeak Squeak VM version: 4.5 4.0.3410 Mac OS X built on Jul 19 2015 04:40:14 UTC Compiler: 4.2.1 (Apple Inc. build 5666) (dot 3) [Production VM] Built from: CoInterpreter VMMaker.oscog-eem.1426 uuid: 94ab92ba-c5c4-4953-8566-a4cd9c38df1f Jul 19 2015 With: StackToRegisterMappingCogit VMMaker.oscog-eem.1427 uuid: c5cb18c5-f69e-4e41-8f87-943a495659b4 Jul 19 2015 Revision: VM: r3410 http://www.squeakvm.org/svn/squeak/branches/Cog Date: 2015-07-18 19:15:20 -0700 Plugins: r3405 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins

C stack backtrace & registers: eax 0x00000016 ebx 0x0dc903b0 ecx 0x01aae35f edx 0x0da8c780 edi 0x0dc90354 esi 0x0dc90354 ebp 0xbff5cc18 esp 0xbff5cbd0 eip 0x000e1535 (0 Squeak 0x000e1535 mapPointersInObjectsFromto + 1461)

Smalltalk stack dump: 0xbff76bd8 M INVALID RECEIVER>inject:into: 0xda9ba34: a(n)

2015-07-21 9:27 GMT+02:00 Sabine Manaa manaa.sabine@gmail.com:

Eliot, is Cog.app-15.28.3410.tgz http://www.mirandabanda.org/files/Cog/VM/VM.r3410/Cog.app-15.28.3410.tgz the right one? Regards Sabine

2015-07-21 9:24 GMT+02:00 Sabine Manaa manaa.sabine@gmail.com:

...

This is production: Windows Server 2008 R2 Datacenter

Development is MacOs

2015-07-20 23:04 GMT+02:00 Stephan Eggermont [via Smalltalk] < ml-node+s1294792n4838441h66@n4.nabble.com>:

...

On 20/07/15 22:55, Eliot Miranda wrote:

...

Are you on Mac OS X or Linux?

Windows Server 2008 R2 Datacenter says the first mail in this thread

Stephan

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... To unsubscribe from pharo 4.0 Crashed in the VM thread again, click here http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4836826&code=bWFuYWEuc2FiaW5lQGdtYWlsLmNvbXw0ODM2ODI2fC0xOTE3OTcxOTg5 . NAML http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

-- View this message in context: http://forum.world.st/pharo-4-0-Crashed-in-the-VM-thread-again-tp4836826p483... Sent from the Squeak VM mailing list archive at Nabble.com.