> On May 3, 2017, at 1:52 PM, Thierry Goubier <[email protected]> wrote: > >> Le 03/05/2017 à 22:39, Eliot Miranda a écrit : >> Hi Thierry, > > Hi Eliot, > >>> On May 3, 2017, at 1:20 PM, Thierry Goubier >>> <[email protected]> wrote: >>> >>> I'm now chasing an old 64 bits vm from files.pharo.org. All the new >>> ones for the past 2 months segfault. Would anybody have kept a ~ 2 >>> month old 64 bits vm (threaded or not) for linux somewhere? >> >> I think the issue is not the version of the VM sources but the >> version of GCC. Iconoile the 64-bit Linux VMs I build with GCC 4.4.x >> and see no problems. Bintray uses 4.6.x and apparently segfaults. >> Are you able to checkout opensmalltalk-vm and build your own 64-bit >> Linux vm using GCC 4.4.x? You may have more success via this route. > > I'm on a system with gcc 6.3.0. The previous stable pharo vm is fine > (20170212) so I'm back on it. None of the newest are, but I haven't done a > bisect to tell you which number triggers the segfault. > > I do have random lockups with OSProcess on it, but they are cured with a > Ctrl+., which is nice. > > I've never managed to get a home-compiled 64 bits vm to work without a > segfault or a deadlock, so I've given up that path (*).
Then I'll try and have a look asap. > > Regards, > > Thierry > > (*) I've never managed to be sure I had all the dependencies right (i.e. > tracking through the long log output and trying to make sure cover all the > errors by loading the right package). I could compile the vm, and run it a > bit (run a few image building commands) before hitting either a deadlock > (OSProcess-related?) or a segfault. > >> HTH >> >>> >>> Regards, >>> >>> Thierry >>> >>>> Le 03/05/2017 à 21:58, Nicolas Cellier a écrit : >>>> >>>> >>>> 2017-05-03 17:45 GMT+02:00 Eliot Miranda >>>> <[email protected] <mailto:[email protected]>>: >>>> >>>> >>>> >>>>> On May 3, 2017, at 4:22 AM, Esteban Lorenzano >>>>> <[email protected] <mailto:[email protected]>> wrote: >>>>> >>>>> >>>>>> On 3 May 2017, at 12:38, Alistair Grant >>>>>> <[email protected] <mailto:[email protected]>> >>>>>> wrote: >>>>>> >>>>>> Hi Esteban, >>>>>> >>>>>> $ curl http://get.pharo.org/64/60+vmLatest >>>> <http://get.pharo.org/64/60+vmLatest> | bash >>>>>> $ ./pharo --version >>>>>> >>>>>> Shows the build version as: >>>>>> >>>>>> VM: 201705022326 >>>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >>>> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >>>>>> Date: Tue May 2 16:26:41 2017 -0700 $ >>>>>> >>>>>> Does that mean we should be building from the opensmalltalk >>>>>> repository instead of the pharo-vm repository (even >>>>>> temporarily)? >>>>> >>>>> officials VM for Pharo now are built using opensmalltalk-vm, >>>>> yes. we still keep our process for CI/testing purposes, >>>>> though. >>>> >>>> Woot! Thank you Esteban!! >>>> >>>> >>>> +1 That will help us to help you, it's a win win. >>>> >>>> >>>>> >>>>> Esteban >>>>> >>>>>> >>>>>> Thanks, Alistair >>>>>> >>>>>> >>>>>>> On 3 May 2017 at 09:43, Esteban Lorenzano >>>>>>> <[email protected] >>>> <mailto:[email protected]>> wrote: >>>>>>> in 15min, I will promote latest VM to stable VM. The new >>>>>>> stable VM has a lot of bugfixes, notably: >>>>>>> >>>>>>> - compactor works - Cairo and Surface plugin now can >>>>>>> coexist (and it does not crashes) - lot of other small >>>>>>> things >>>>>>> >>>>>>> cheers, Esteban >>>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
