Hello all,
I seem to be having a problem rebuilding the Mac 2.1 VM. It compiles and links just fine, but then I get an unrecoverable error on the first file access. Has anyone else seen this behavior? I'm using CodeWarrior 11 Gold.
....any advice appreciated...
stp
_ Stephen Travis Pope _ Center for Research in Electronic Art Technology (CREATE) _ Department of Music, Univ. of California, Santa Barbara (UCSB) _ stp@create.ucsb.edu, http://www.create.ucsb.edu/~stp/
STP,
I just rebuilt a Mac 2.1 VM from a virgin image this morning using CodeWarrior 10 Gold, and it appears to be working fine. This is good news, bad news. The good news is that there probably is nothing wrong with the Squeak side. The bad news is that your C side is probably screwed up. You'll have to round up the usual suspects -- changed libraries, changed headers, etc.
BTW, which unrecoverable error do you get ?
Jim
At 10:04 AM -0700 8/10/98, Jim Benson wrote:
STP,
I just rebuilt a Mac 2.1 VM from a virgin image this morning using CodeWarrior 10 Gold, and it appears to be working fine. This is good news, bad news. The good news is that there probably is nothing wrong with the Squeak side. The bad news is that your C side is probably screwed up. You'll have to round up the usual suspects -- changed libraries, changed headers, etc.
BTW, which unrecoverable error do you get ?
Jim
Thanks for verifying this, Jim!
The image STP is trying to open may be too large for the default memory partition of the VM. Try using the "get info" command of the finder to increase the memory allocation of the newly built VM.
STP, let us know if this helps. If so, we should probably add this to the Swiki somewhere.
-- John
Maloney wrote:
The image STP is trying to open may be too large for the default memory partition of the VM. Try using the "get info" command of the finder to increase the memory allocation of the newly built VM.
John,
In this case, I believe that Squeak screams:
Insufficient memory for this image
in the stdout window, and things quickly come to a grinding halt. Saying that, I have encountered borderline sized images that load but do not remain happy for very long.
Now, you mention using a modified image to test your VM. This can lead to many hours of debugging fun!!! I have spent many hours entertaining myself in the C debugger trying to figure why my newly spawned VMs do not work properly. Invariably, I generate a VM from an image, and unknowingly try to run another image on it that has special primitives or API calls within (images with different primitive numberings are especially fun). Oh how I love seeing the MacsBug monitor smiling at me. When things go south, rule number one is to test the distributed standard image with the newly generated VM.
Learned the hard, expensive way,
jb
squeak-dev@lists.squeakfoundation.org