VM crash at startup - startup activeProcess corrupt?

Ben Schroeder bschroeder at procro.com
Tue May 11 19:02:14 UTC 2004

Hi Tim,

> The simplest thing to suspect here is that the image write failed part
> way through dumping memory. How big is the image file? How 
> big does the
> image header _think_ it is?

The image header thinks the object memory is

	15799376 bytes

and the file is

	15799440 bytes

which matches (object memory size + 64-byte header size).

But what you say might still be the cause: the image file was on a shared network drive, which could introduce its own wrinkle.  Maybe the network write caused the file to be preallocated to be the right size, and zeroed out, but the bits never made it?

By the way - thanks for your "Tour of the Squeak Object Engine" book chapter - it, of course along with the Squeak sources, has been a big help in picking through the image file.

Ben Schroeder

More information about the Squeak-dev mailing list