Mike Frysinger wrote: > all documentation on vfork() is very clear: the only thing you can rely on > portably after a vfork() is to call _exit() or an exec() function.
That's what POSIX says. It turns out even that may not be safe: some versions of Glibc call malloc() and realloc() inside execvp() and execlp(), which is to say the least risky. -- Jamie _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
