Hi folk,
I'm porting uClinux to our new no-mmu architecture.
There is a trouble occured.
After system call vfork() is called, the parent is suspended and
cannot continue executing until the child exits or calls exec(),
the system call used to start a new application.
The child, directly after returning from vfork(),
is running on the parent's stack and is using the parent's memory and
data.
This means the child can corrupt the data structures or the stack in the
parent, resulting in failure.
How can I avoid the problem? Is there any solution?
Thanks!
Best regards,
Ahan Hsieh
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
