Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!bionet!uwm.edu!spool.mu.edu!munnari.oz.au!ariel!ucsvc.ucs.unimelb.edu.au!wehi.dn.mu.oz!baxter_a
From: baxter_a@wehi.dn.mu.oz
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Kill and Getting Killed, heh.
Message-ID: <1991May17.193234.24598@wehi.dn.mu.oz>
Date: 17 May 91 19:32:34 GMT
References: <378.2830d367@beach.gal.utexas.edu> <1228@cbmger.UUCP>
Organization: Walter & Eliza Hall Institute
Lines: 20

In article <1228@cbmger.UUCP>, peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
...
> Oh huh, this one again. (You know, we have such discussions at least
> every four weeks.)
> Now, there is no kill command *possible* in AmigaDOS, because we have
> no resource tracking, mainly for performance and compatibility reasons.
> So the OS doesn't know what memory or file locks are occupied by this
> task and thus can't free them (e.g. screens/windows, etc.). To say it
> clearly: Yes you can stop a program (there are PD tools like Xoper
> available), but you can't free all resources. So this is of not much use.
> (Please *not again* this resource tracking discussion, noooo!!)


Okay, fine. But why can't a symbolic debugger handle allocation/return
type issues. I've been hunting an 800 byte memory loss with SDB (Lattice)
for 2 weeks. If the debugger maintained a list of resources allocated and
returned, it would be able to give me the location of the lost memory
and what line allocated it.

Regards Alan