Why not launch the "child" simply as a separate process through either fork+exec or just system, depending on your OS?
That way, it would be trivial and obvious that the child runs with the latest of the greatest of modules.
You will need to arrange for the transfer of the payload to the child somehow, but most likely a temporary file or something like that will be enough.
In reply to Re: Server launching external process without copying memory
by Corion
in thread Server launching external process without copying memory
by mathieu
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |