[Openmcl-devel] forking to dump?

Tobias C. Rittweiler tcr at freebits.de
Thu Jul 10 06:44:59 UTC 2008


"Hans Hübner" <hans at huebner.org> writes:

> On Thu, Jul 10, 2008 at 08:16, Tobias C. Rittweiler <tcr at freebits.de> wrote:
>
> > But if S-A modifies the heap of the child, doesn't it also modify the
> > heap of the parent, possibly corrupting it?
>
> fork() creates a new child process with a copy of the memory image of
> the parent process.  It is normally implemented using copy-on-write
> pages.  The child process has no access to the parent's memory image,
> so it can't corrupt it's heap.  

So what's the locking problem Gary is talking about? (I could imagine
that the copied states of condition variables etc. may cause problems
when loading the image back in, and trying to get the image working
again; but Gary seems to be talking about locking problems prior to
dumping.)

  -T.




More information about the Openmcl-devel mailing list