| error handling child process [message #7550] |
Mon, 09 December 1996 00:00 |
george
Messages: 22
Registered: August 1996
|
Junior Member |
|
|
Wow, I have 95MB of swap space available, but my idl process is
bigger. Gobbling and gobbling disk space seems to me an ugly solution.
What I am going to do is re-write my widget programs without data
variable parameters in the procedure call. Right now I am passing my
data cubes as parameters thereby forcing myself to make a copy of the
data variable for the common block variable name needed in widgets.
Thank you for pointing me in the right direction, vis-a-vis the spawn
error and swapping.
Can you think of another way around the problem in IDL. Can one
interact with a process which is not a subprocess of idl, to work with
the system the some do, but in a way that avoids swapping the whole idl
process out like for a spawn.
George McCabe, HSTX @ NASA/GSFC, george.mccabe@gsfc.nasa.gov
On Mon, 09 Dec 1996 16:38:36 -0500, Phil Williams wrote:
> If it still fails with the noshell keyword then I think that the only
> solution is to add more swap space to your system.
>
> I think that you are correct in your statement that the allocated memory
> is in common blocks. They only way that I know to reduce that is to
> issue the common statement for the block of interest and zero out all
> the variables.
>
> Good luck,
> Phil
>
> George McCabe wrote:
>>
>> Phil, yes it is unix (SGI IRIX). I am sorry to say, /noshell doesn't
>> work.
>>
>> IDL> spawn,["ls"],listing
>> % SPAWN: Error managing child process.
>> Resource temporarily unavailable
>> % Execution halted at: $MAIN$
>>
>> IDL> spawn,["ls"],listing,/noshell
>> % SPAWN: Error managing child process.
>> Resource temporarily unavailable
>> % Execution halted at: $MAIN$
>>
>> If I delvar all the variables in $MAIN$, there is still a large amount
>> of memory being used,
>>
>> IDL> help,/memory
>> heap memory in use: 44491251, calls to MALLOC: 110618, FREE:
>> 110249
>>
>> Am I right to think that allocated memory is in common blocks, and if
>> so, what is the way to delete common block allocation. My goal is
>> still to SPAWN a child process, which several of my procedures do. The
>> only other thing that I can think of is to arrange for enough swap
>> space to set aside the IDL process in memory (as you described).
>>
>> Thank you, George McCabe, HSTX @ NASA/GSFC, george.mccabe@gsfc.nasa.gov
>
> --
> /*********************************************************** ********/
> Phil Williams, Ph.D.
> Research Instructor
> Children's Hospital Medical Center "One man gathers what
> Imaging Research Center another man spills..."
> 3333 Burnet Ave. -The Grateful Dead
> Cincinnati, OH 45229
> email: williams@irc.chmcc.org
> URL: http://scuttle.chmcc.org/~williams/
> /*********************************************************** ********/
>
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||||||||||
George McCabe (HSTX) NASA / GSFC
Tel: (301)286-8283, Fax: (301)286-0212 Code 693, B2 R151
E-mail: george.mccabe@gsfc.nasa.gov Greenbelt, MD 20771
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
