2017-11-22 13:03 GMT+01:00 Gabriel Cotelli <g.cotelli@gmail.com>:
Well that make sense. The problem is that the stable VM is crashing with a segmentation fault :( on Linux/64 bits.

I can confirm.

Given that later vms do not segfault, Eliot told me he prefers to consider the bug(*) solved.

Thierry

(*) But I have no idea about what the bug is. Running the stable pharo vm under valgrind also triggers the segfault, valgrind complains a lot and signal permamently lost memory, but this is the same with all vms as far as valgrind is concerned (i.e. non-crashing and even non-pharo vms are no better, except that they don't crash).
��

On Nov 22, 2017 08:46, "Esteban Lorenzano" <estebanlm@gmail.com> wrote:


On 21 Nov 2017, at 21:00, Gabriel Cotelli <g.cotelli@gmail.com> wrote:

I can't find a latest 6.1 vm so I tried with the Pharo 7 Latest VM (wget -O- get.pharo.org/64/vmTLatest70 | bash) and the 6.1 image but crashes with a segmentation fault also.

by concept, there is no ���latest 6.1 vm��� since latest is ���unstable��� (alpha) and 6.1 is not (or it shouldn���t).

latest is always related to the development version.

Esteban


On Tue, Nov 21, 2017 at 12:03 PM, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Hi Gabriel,

I had such segfaults��with the stable 6.1/64bits on Linux. I solved them by ensuring the use of a more recent version than the stable one.

Thierry


2017-11-21 15:56 GMT+01:00 Gabriel Cotelli <g.cotelli@gmail.com>:
I've created the following issue:
I can reproduce it easily so if you need some more info let me know.

Regards,
Gabriel