After loading an existing state in a fresh session, I find that previously defined calls to C functions (saved in the state) crash the session if (and only if) the foreign call was called in an earlier session before the state was saved. I can supply an example if necessary.

After investigating, it is actually malloc that is failing in the calls. Surprisingly, the very first malloc in the session finds an existing address. As freeList is emptied by PolyML.onEntry presumably freeList is being restored by loadState. Does that sound like an issue? I would expect that the freeList state is untouched by loadState.

Phil
_______________________________________________
polyml mailing list
polyml@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml

Reply via email to