On Fri, 30 Jan 2004, Jacques Garrigue wrote:

> However, there is another scenario which could cause you problems:
> if for some reason your C pointer get freed, and later the ML heap is
> extended so that it includes the address of the pointer, then you may
> have some pointers left on the ML which will now be seen as ML
> pointers.

ML doesn't memset memory it just allocated?  This may be a problem- I 
don't *think* the C standard requires malloc to memset the memory itself, 
which means you might be getting garbage memory.

-- 
"Usenet is like a herd of performing elephants with diarrhea -- massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
                                - Gene Spafford 
Brian

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners