I've created the following issue:
I can reproduce it easily so if you need some more info let me know. Regards, Gabriel |
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 <[hidden email]>:
|
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. On Tue, Nov 21, 2017 at 12:03 PM, Thierry Goubier <[hidden email]> wrote:
|
Le 21/11/2017 à 21:00, Gabriel Cotelli a écrit :
> 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 <http://get.pharo.org/64/vmTLatest70> | > bash) and the 6.1 image but crashes with a segmentation fault also. I also have a segfault with vmTLatest70. At the moment, I use cog_linux64x64_pharo.cog.spur_201711061254, and this one doesn't segfault. Otherwise, you can use the snap version of Pharo. This one doesn't segfault. You may have to install snap on your linux mint, and the snap has effect when you're calling external commands from Pharo. Thierry > > On Tue, Nov 21, 2017 at 12:03 PM, Thierry Goubier > <[hidden email] <mailto:[hidden email]>> 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 <[hidden email] > <mailto:[hidden email]>>: > > I've created the following issue: > > https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-code-into-a-64-bits-Pharo-6-1-Linux > <https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-code-into-a-64-bits-Pharo-6-1-Linux> > I can reproduce it easily so if you need some more info let me know. > > Regards, > Gabriel > > > |
In reply to this post by gcotelli
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
|
Well that make sense. The problem is that the stable VM is crashing with a segmentation fault :( on Linux/64 bits. On Nov 22, 2017 08:46, "Esteban Lorenzano" <[hidden email]> wrote:
|
2017-11-22 13:03 GMT+01:00 Gabriel Cotelli <[hidden email]>:
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).
|
Hi all
so what is the situation? Is the latest version crashing? Stef On Wed, Nov 22, 2017 at 1:18 PM, Thierry Goubier <[hidden email]> wrote: > > > 2017-11-22 13:03 GMT+01:00 Gabriel Cotelli <[hidden email]>: >> >> 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" <[hidden email]> wrote: >>> >>> >>> >>> On 21 Nov 2017, at 21:00, Gabriel Cotelli <[hidden email]> 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 >>> <[hidden email]> 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 <[hidden email]>: >>>>> >>>>> I've created the following issue: >>>>> >>>>> >>>>> https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-code-into-a-64-bits-Pharo-6-1-Linux >>>>> I can reproduce it easily so if you need some more info let me know. >>>>> >>>>> Regards, >>>>> Gabriel >>>> >>>> >>> >>> > |
Hi Stéphane,
Le 25/11/2017 à 14:08, Stephane Ducasse a écrit : > Hi all > > so what is the situation? When I tested, and following Gabriel input, all the zeroconf vms for Pharo61 or 7 linux 64bits segfault (stable or latest, thread). Recent vms for pharo linux 64bits downloaded from opensmalltalk do not segfault. Thierry > Is the latest version crashing? > > Stef > > On Wed, Nov 22, 2017 at 1:18 PM, Thierry Goubier > <[hidden email]> wrote: >> >> >> 2017-11-22 13:03 GMT+01:00 Gabriel Cotelli <[hidden email]>: >>> >>> 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" <[hidden email]> wrote: >>>> >>>> >>>> >>>> On 21 Nov 2017, at 21:00, Gabriel Cotelli <[hidden email]> 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 >>>> <[hidden email]> 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 <[hidden email]>: >>>>>> >>>>>> I've created the following issue: >>>>>> >>>>>> >>>>>> https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-code-into-a-64-bits-Pharo-6-1-Linux >>>>>> I can reproduce it easily so if you need some more info let me know. >>>>>> >>>>>> Regards, >>>>>> Gabriel >>>>> >>>>> >>>> >>>> >> > > |
Free forum by Nabble | Edit this page |