site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Thread-index: Ace8Lx0JW8MdmCgiEdyG7QAWy4i6sA== Thread-topic: Fork, exec, and child inheritance oh my User-agent: Microsoft-Entourage/11.3.3.061214 on 7/1/07 5:07 PM, Dave Keck at davekeck@gmail.com wrote:

Right now I've been walking the dark alleys of fork(), execv(), and mmap(), but I'm not seeing much light. It seems what we need is a version of execv() that wouldn't completely overwrite the parent process, so that the parent and child would share the same address space and both able to access the symbols loaded by the child process.

The problem is that parent and child processes never "share" the same address space. When the child process changes memory, a copy-on-write page fault occurs, giving the child it's own copy of the changed memory. The parent process memory is unchanged. Perhaps you could explain why you don't want the parent process to simply load the code itself? Paul Nelson Thursby Software Systems, Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com