Path: utzoo!attcan!uunet!van-bc!mdivax1!mclaren
Newsgroups: mu.mcug.commodore.amiga,comp.sys.amiga.tech
Subject: Re: Killing a Process
Summary: You can't do it gracefully
Keywords: memory, tasks, infinite
Message-ID: <1990Nov2.022951.7409@mdivax1.uucp>
Date: 2 Nov 90 02:29:51 GMT
References: <90305.102608CD7HOPER@MIAMIU.BITNET>
Reply-To: mdivax1!mclaren (Gavin McLaren)
Organization: Mobile Data International, Richmond, B.C., Canada
Lines: 22
Return-Path: <mdivax1!news>
Apparently-To: van-bc!rnews

Ok.  There were two questions really.

1) Can I kill a running task.

2) Can I recover the resources used by that task.

The answer to 1) is definitely yes.  There are no system commands that
help out, however.  GOMF (a commercial product) offers a command called
'nuke' that allows you to remove a task from the system, and remove graphics
elements (screens, windows) that were associated with the task.  I think
that the bitmap memory automatically allocated by the system for these
items is also released.

However, my understanding is that you will NOT be able to recover all the
memory used by the program.  The code and data areas should be able to be
unloaded, along with any memory that was added to the SegList in the
task structure.  However, memory obtained through AllocMem() must be returned
by FreeMem(), and memory allocated with malloc() may or may not be added to the
segment list.


--Gavin McLaren			..!{uucp}!mdivax1.uucp!mclaren