Hi John,
You know what ... let's fix this problem for real. I've spent a bit of time looking through what happens and I'm certain now that the root bit problem only affects the active and the home context. If it were any different we would have been crashing all the time as the original problem showed quite nicely (it was _very_ reliable once you triggered a store into activeCtx ;-)
I've just been doing a little cleanup anyway (there is so much code duplication between primitiveSnapshot and primitiveSnapshotEmbedded) so I'll just add the external prim flushing to it and clean out the root bit. The root bit in the active context can act as the trigger for doing the full cleanup otherwise we rely on a cleanly saved image. BTW, I have checked it and the root bit of the active context _is_ set in all Squeak images back to 1.1 ;-) so we won't have any nasty surprises.
So do we have any other cleanup we'd like to do upon image save? This is a good time to mention it.
Cheers, - Andreas
-----Original Message----- From: squeak-dev-bounces@lists.squeakfoundation.org [mailto:squeak-dev-bounces@lists.squeakfoundation.org] On Behalf Of John M McIntosh Sent: Wednesday, August 06, 2003 11:08 PM To: The general-purpose Squeak developers list Subject: Re: [ENH][VM] faster image startup
On Wednesday, August 6, 2003, at 01:26 PM, Andreas Raab wrote:
Yuck! Why don't you grab it from the end of the object
memory itself?
E.g., simply adjusting endOfMemory to just after the end of the
OM will give
you _lots_ of space for recording the CMs
Ah, hadn't considered that, I'll redo the change set.
We got at least 100,000 bytes there (usually mb more in reality) and I only need 16k or so.
--
==========
John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
==============================================================
===