At 5:55 PM +0200 3/18/02, Peter Gibbs wrote:
>Dan
>
>I have been reading memory.c and resources.c trying to understand how memory
>allocation and garbage collection works, and have found what looks to be a
>bug.
>
>The initial allocation routine in mem_setup_allocator creates two blocks,
>one for the free string header pool and one for the free pmc header pool.
>However, Parrot_go_collect copies only the free string header pool to the
>newly allocated block (followed by the compacted strings), then proceeds to
>free the entire memory pool - what happens to the free pmc header pool??
D'oh! thanks for the catch. I'll go fix.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
