Article View: comp.sys.amiga.tech
Article #9849Memory tracing and protection code
From: Jon Wesener
Date: Tue, 20 Sep 1988 01:28
Date: Tue, 20 Sep 1988 01:28
21 lines
1401 bytes
1401 bytes
1st, I developed some routines for stopping me from crashing my
amy by freeing up memory twice and not freeing up memory allocated
by AllocMem. These routines will stop memory from being freed up
that isn't allocated and the at the end of your program it will free
up memory that wasn't freed up. But, when it comes across either of
these conditions it will print out the name of the file, function and
line number of the offending call or the file, func and line of an
alloc that wasn't freed up.
I don't know if something like this has been posted already since it
was soooo easy to write and soooo useful that I'm not posting now in case
there might be something out which does it already or if no one wants it.
Anyone interested?
--j
--
... {seismo | harvard } ! {uwvax | cs.wisc.edu} ! astroatc!jojo
"They weren't just any women... They were women fresh from Hell, with
wisps of devil-smoke curling behind their ears and unholy vapors hiding
in their tight leather dresses, looking for Mr. Right."
Technical Details
Message-ID:
<1194@astroatc.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!astroatc!jojoShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!astroatc!jojo From: jojo@astroatc.UUCP (Jon Wesener) Newsgroups: comp.sys.amiga.tech Subject: Memory tracing and protection code Message-ID: <1194@astroatc.UUCP> Date: 20 Sep 88 01:28:34 GMT Organization: Astronautics Technology Cntr, Madison, WI Lines: 21