Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!cbmehq!cbmger!peterk
From: peterk@cbmger.UUCP (Peter Kittel GERMANY)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Kill and Getting Killed, heh.
Message-ID: <1237@cbmger.UUCP>
Date: 22 May 91 07:29:15 GMT
References: <378.2830d367@beach.gal.utexas.edu> <1228@cbmger.UUCP> <1991May17.193234.24598@wehi.dn.mu.oz>
Reply-To: peterk@cbmger.UUCP (Peter Kittel GERMANY)
Organization: Commodore Bueromaschinen GmbH, West Germany
Lines: 18

In article <1991May17.193234.24598@wehi.dn.mu.oz> baxter_a@wehi.dn.mu.oz writes:
>In article <1228@cbmger.UUCP>, peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
>...
>> (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.

Well, as the OS doesn't do it, every program is responsible to maintain
and track its resources. If you see such a loss when using SDB, it's
certainly a fault of SDB.

-- 
Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk