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:27:38 -0600
On Jul 31, 2011, at 1:59 AM, vincent habchi wrote:
> Thanks for these precisions. Actually, you’re right with fork (2), but vfork (2), AFAIK, does not copy anything; note that I’m aware that vfork usually is meant to be immediately followed by exec (3).
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.
--
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