Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!unido!rmi!infoac!infohh!shimoda
From: shimoda@infohh.rmi.de (Markus Schmidt)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Resource tracking routines for C programmers
Message-ID: <492@infohh.rmi.de>
Date: 3 Feb 89 19:01:38 GMT
References: <3374@sugar.uu.net>
Reply-To: shimoda@infohh.rmi.de (Markus Schmidt)
Organization: RMI Net * Aachen/Hamburg/Flensburg * W.Germany
Lines: 17

In article <3374@sugar.uu.net> karl@sugar.uu.net (Karl Lehenbauer) writes:
>Those resource monitoring routines I wrote for C programmers and posted here
>in comp.sys.amiga.tech seem to me to be the answer to the prayers of C
>people who are trying to locate and/or determine if they have memory 
>leaks, yet it went by with nary a whisper.  Did anyone see them/think they
>were useful/do anything with them?
Yes, me. I didnt had the time to try 'em yet but I will sure
do.


.-----------------------------------------------------------------.
|  shimoda@rmi.de       `---'   The last remaining adventure      |
|  shimoda@gopnbg.UUCP  |O o|   since there are no more tigers:   |
|                       ==Y==   Doublebuffered async. I/O       _ |
|----------------------- `U' ------------------------------  _ // |
|  Good terminalpackages     begin with A: AmigaCall, A-Ta.. \//  |
`-----------------------------------------------------------------'