Re: pexec bug in MiNT?

[Brent Thirsk <thirsk@telusplanet.net>]

Katherine L Ellis wrote:

> 1) I use beta 1.15 latest . Might be a diff with 1.14.7, Do I need to
> force a Pterm after the pexec?
By force, if you mean from the parent, some process you cannot force
term. The child process should pterm() itself.
> Do I need to really check the return status of the child? if yes with
> pwait? 
not necessary, unless there was an error, which ussually is not the
 case.
> 2) The child I pexec is munpack 1.5. Which seeems to be buggy anyway.
> Stack problem. This was compiled with purec I think. I couldn't fixstk
> it. Anyone has a gnuc compiled version of it?
> 3) Do I need to allocate extra ram for the child? even if I use pexec
> mode 0?
Only if parent process is a memory hog and allocates all available
memory for itself. You then have to release memory and allocate as ness.
I limit most programs to 310k, to avoid use of malloc() which seems to
cause more problems than not.
I have also found running parent process in ST ram and child in FAST ram
seems to avoid any conflicts. As my parent processes are menu programs,
they don't need to be in FAST ram anyway. They hardley ever do anything. 
> Thanks.
> ________________________________________________________________________________
> Email:Kellis@primenet.com
> Web http://www.primenet.com/~kellis/
> ________________________________________________________________________________

-- 
Brent
Thirsk Engine /Ponoka/Alberta/Canada
http://www.telusplanet.net/public/thirsk/thirsk_web_page/index.htm
Email  thirsk@telusplanet.net