What exactly are the semantics of the GC_ALLOC_FIXED option to gc_malloc? Is it a hint that the new object has no references to other objects (hence walkNull), or is it to tell a moving collector that the object shouldn't be moved? Or is it something else? On the same note, what exactly is the difference between GC_ALLOC_NORMAL and GC_NORMAL_OBJECT? (As of kaffe-1.0.b3, the only mention of GC_ALLOC_NORMAL in the code is for the allocation of the UTF8 constant intern hash-table.) I'm using Kaffe 1.0.b3 on Linux 2.0.30. -- Dave D.W.Hughes@exeter.ac.uk Department of Computer Science, University of Exeter, UK --- ${HOME} is where the .emacs is. ---