Re: Return causes EXC_BAD_ACCESS
Re: Return causes EXC_BAD_ACCESS
- Subject: Re: Return causes EXC_BAD_ACCESS
- From: Scott Ribe <email@hidden>
- Date: Sun, 31 Jul 2011 08:35:36 -0600
On Jul 31, 2011, at 8:27 AM, Scott Ribe wrote:
> No, fork copies the entire address space when it is called, but vfork works as he described. In neither case will modifications to memory by one process by visible by the other.
Oh, hogwash. Of course copy-on-write is a common optimization to fork. And with vfork modifications can be visible to the other process, but the calling process is suspended until the new process exits or calls exec, so it's not useful for interprocess communication, just a side effect available very briefly.
Sorry for the prior noise.
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden