Re: [gccsdk] fork/exec problems

In message <8372408c52.Jo@hobbes.bass-software.com>
John Tytgat <John.Tytgat@aaug.net> wrote:

> You have to be aware of fork() vs vfork() differences. One of those
> is that the child create with vfork() is sharing the same parent's
> address space, while fork() makes a complete copy. That explains your
> observation of wimpslot size changes with fork() and also why this
> can only happen in Wimp context.

Also the implementation in UnixLib is relatively simple, it moves the
parent code at the end of application space, let the child run until it
finishes and parent continues. So this does not end up with an extra
Wimp task, nor it allows you to have concurrently running parent & child.

John.
--
John Tytgat, in his comfy chair at home BASS
John.Tytgat@aaug.net ARM powered, RISC OS driven

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK