Re: [configure.ac/uClinux] Adding code for fork/vfork?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Apr 16, 2011 at 01:53, Bob Friesenhahn
<bfriesen@xxxxxxxxxxxxxxxxxxx> wrote:
> On Fri, 15 Apr 2011, Mike Frysinger wrote:
>>>
>>> If you do not want to "force" people to change their code, you will
>>> probably need to offer a "stub" fork() to link against on non-MMU CPUs.
>>
>> the majority of the time, it isnt just fork() that needs to change.  any
>> exit() in the child needs to be changed to _exit() too.
>
> The sole purpose of vfork is to immediately invoke exec()  Any other purpose
> is forbidden.  In what case would an exit even be required?
>

exec() may fail.  And you need to exit somehow.  Calling of exit() in
such situation is a bad thing because it call atexit handlers.  Thus
you need _exit().

-- 
Andrew W. Nosenko <andrew.w.nosenko@xxxxxxxxx>

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf



[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux