2015-03-06 15:43 GMT+01:00 Max Leske <[email protected]>: > > On 06 Mar 2015, at 15:35, Thierry Goubier <[email protected]> > wrote: > > > > 2015-03-06 15:21 GMT+01:00 Max Leske <[email protected]>: > >> >> On 06 Mar 2015, at 14:56, Thierry Goubier <[email protected]> >> wrote: >> >> Ok. It's not an image problem. It seems to be a vm problem or an ubuntu >> problem. >> >> (vm and vmLatest from get.pharo.org have that, the vm in the pharo >> launcher seems to work fine, and I haven't seen any problem with Pharo3 ? >> Ubuntu 14.10 64bits). >> >> >> Ok, so we need to find the VM version that breaks OSProcess... >> > > I tried to rebuilt a vm from the git for pharo-vm, and it failed at the > end of the process... lots of incorrect function redefinitions in cogit.c, > if it says anything. > > > Yes, I know that. It's a problem with gcc. To fix it and get a working VM > you can use the following: > > /* pre-empty some preprocessor variables used in srv/vm/cogit.h, > cointer.h, etc */ > > # define NoDbgRegParms > # define NeverInline >
In which header do you add that? > > > Note. The pharo launcher vm and the get.pharo.org vm are very similar (5 > days difference), but compiled on very different systems (gcc version and > linux kernel version). > > > Interesting. Do you have a test case that I could try on my machine? > > It's a bit a by hand process, but it should be scriptable :( mkdir pharo cd pharo; wget -O- get.pharo.org/40+vmLatest | bash cd .. pharo/pharo pharo/Pharo.image --no-default-preferences eval --save Metacello new baseline: \'FileTree\'\; repository: \'github://dalehenrich/filetree:pharo4.0_dev/repository\'\; load: \'Git\' pharo/pharo pharo/Pharo.image --no-default-preferences eval --save Gofer new url: \'gitfiletree:// github.com/dalehenrich/filetree?branch=pharo4.0_dev\&dir=repository\'\; package: \'MonticelloFileTree-Tests\'\; package: \'MonticelloFileTree-GitTests\' pharo/pharo pharo/Pharo.image --no-default-preferences test "*GitTests" In my case, it gets stuck somewhere randomly in the process. It could even reach the end (I've seen it deadlock at the very last test :(). If, on the last line, I use the pharo-vm-nox of pharo-launcher, then it will run all tests. Thierry
