Re: [Caml-list] memory corruption with Weak.t in Gc.finalise

[Goswin von Brederlow <goswin-v-b@web.de>]

On Mon, Mar 14, 2016 at 05:44:28PM +0100, François Bobot wrote:
> On 14/03/2016 11:32, Goswin von Brederlow wrote:
> >
> >Still using 4.02. This is a new thing.
> >
> >Still Weak.t needs to interact cleanly with the Gc. Guessing at the
> >internal state of Weak.t is bad. Let's fix this for 4.03.
> 
> I think it is already fixed for 4.03. The new GC phase named "clean",
> between mark and sweep, makes the behavior of weak pointers straightforward
> compared to previous OCaml version:
>  - A weak pointer is unset only if the value pointed is marked dead after
> the mark phase (ie. no way to ever access it, the memory could be freed).
>  - Conversely, during the clean phase, a weak pointer to a dead value is
> considered unset (so Weak.get return None).
> 
> If you know weird behavior in 4.03+beta on weak pointers or ephemeron, I
> would be very interested to know them.
> 
> Best,

I heard about that design cleanup. But what I ment was to provide and
document an interface for C code interacting with Weak.t.

MfG
	Goswin