I figured that might be the case. I'll stick with Elliot's latest builds for now, but I'll have to revisit it once I start working on Pharo 2.0 compatibility, as the 2.0 images complain about the VM being too old (kind of funny considering the Pharo VMs appaear to be based on older Cog code in the first place).
At the moment I'm still working on getting through the tests on 1.3. Haven't had a whole lot of time this week, but I should be able to make some real progress next week.
On 10 January 2013 04:52, Chris Muller ma.chris.m@gmail.com wrote:
Ok when I test with this VM it crashes just like Eliots older Cog VMs (the ones prior to 2640) in exactly the same spot -- in the #testSequenceNumberGenerator test.
The best way to work on Magma on Pharo is simply to run with the latest Cog VM's or with the "classic" (non-Cog) VM.
- Chris
On Mon, Jan 7, 2013 at 4:00 PM, Stuart Herring st-lists@stuartherring.com wrote:
Here's the VM I was using: http://pharo.gforge.inria.fr/ci/vm/cog/linux/cog-linux-latest.zip
On 8 January 2013 02:27, Chris Muller asqueaker@gmail.com wrote:
Wow, that's strange! I can't think of anything in Magma that should be affected by the VM like that.
Maybe the Pharo VM is exposing a Magma problem that the standard Cog VM doesn't? I'd like to debug it to make sure. Where can I find the failing VM you're using?