[GitHub] [incubator-nuttx] v01d opened a new issue #3334: execv() AND vfork()

[GitBox <gi...@apache.org>]

v01d opened a new issue #3334:
URL: https://github.com/apache/incubator-nuttx/issues/3334


   ```
     Description: There is a problem when vfork() calls execv() (or execl()) to
                  start a new application:  When the parent thread calls vfork()
                  it receives and gets the pid of the vforked task, and *not*
                  the pid of the desired execv'ed application.
   
                  The same tasking arrangement is used by the standard function
                  posix_spawn().  However, posix_spawn uses the non-standard, internal
                  NuttX interface task_reparent() to replace the child's parent task
                  with the caller of posix_spawn().  That cannot be done with vfork()
                  because we don't know what vfork() is going to do.
   
                  Any solution to this is either very difficult or impossible without
                  an MMU.
     Status:      Open
     Priority:    Low (it might as well be low since it isn't going to be fixed).
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org