On 07/03/13 15:58, Sven Van Caekenberghe wrote:
I am getting crazy, it seems to be pretty random, sometimes it works,
most of the time it doesn't.
Well, if it sometimes happen and sometimes not and on other machines
the same binary works like a charm, I would say this is due to a
memory corruption - but you probably know that already :-)
The crash in #becomeForward: is likely as it scans whole memory
and sooner or later, it hit the corrupt object. So I think the
#becomeForward: is probably not the bad guy here.
On 07 Mar 2013, at 16:40, Esteban Lorenzano <[email protected]
<mailto:[email protected]>> wrote:
vm version?
On both 32 and 64 bit...
On Mar 7, 2013, at 4:35 PM, Sven Van Caekenberghe <[email protected]
<mailto:[email protected]>> wrote:
On 07 Mar 2013, at 15:31, Sven Van Caekenberghe <[email protected]
<mailto:[email protected]>> wrote:
I am still investigating, but it seems things changed in the Ubuntu
universe regarding ia32-libs on 64 bit (it does no longer exist).
Maybe that is a factor as well, I am not sure.
I just installed a fresh 64-bit Ubuntu 12.10 Desktop in VirtualBox
and tried my build there.
sudo apt-get install ia32-libs
is like a virtual package now that installs :i386 versions of already
installed libraries (or something like that).
Anyway, the VM worked but crashed when doing my build, again in
#becomeForward:
So it looks like is related to 32/64 bit differences.
What kind of Linux machines are the build slaves in the CI
infrastructure ?
Sven
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill
