[Gc] GC_invoke_finalizers () problem still there
Tue, 1 Jul 2003 11:06:46 -0700
The current version looks OK to me.
Mem_freed_before is only read if count != 0. For that to happen, we must have executed
the code that initializes mem_freed_before in the loop.
This is a bit baroque, but it lets GC_mem_freed be read while the lock held is for other reasons.
> -----Original Message-----
> From: Varga Zoltan [mailto:firstname.lastname@example.org]
> Sent: Tuesday, July 01, 2003 2:46 AM
> To: email@example.com
> Subject: [Gc] GC_invoke_finalizers () problem still there
> According to the recent_changes file, the uninitialized
> memory problem
> in GC_invoke_finalizers () is fixed in 6.2pre6, but looking
> at the code,
> it is still there, i.e. if GC_finalize_now is 0, then
> is not initialized.
> Gc mailing list