Article View: comp.sys.amiga.tech
Article #653Re: Catching free memory violations
From: Andy Heffernan
Date: Sat, 29 Jul 1989 17:48
Date: Sat, 29 Jul 1989 17:48
22 lines
1543 bytes
1543 bytes
In article <7413@ecsvax.UUCP> utoddl@ecsvax.UUCP (Todd M. Lewis) writes: >Actually, what I had in mind was to do a SetFunction() on >FreeMem() so I could monitor ALL the free memory in the system, >not just for programs I may be writing. I would really like >to run this when I'm trying out other peoples programs (not than >anyone reading this would write programs with bugs:). Sound like you could use Snoop, which probably is still on the Toolkit disk which is or was offered from CATS. See the Introductory postings for the required info. Snoop will put descriptions of each AllocMem and FreeMem call (via SetFunction()'s) out the serial port at 9600 bps, so hook up a fast terminal and watch the world go by. And while you have the terminal hooked up, you can play with RomWACK, too. -- ------------------------------------------------------------------------- Andy Heffernan uunet!glyph!nichiren [1222 - 1282] ------------------------------------------------------------------------- "Dogpile on the rabbit! Dogpile on the rabbit!"
Technical Details
Message-ID:
<473@glyph.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!glyph!nichirenReferences:
<7408@ecsvax.UUCP> <3965@cps3xx.UUCP> <7413@ecsvax.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!glyph!nichiren From: nichiren@glyph.UUCP (Andy Heffernan) Newsgroups: comp.sys.amiga.tech Subject: Re: Catching free memory violations Keywords: FreeMem monitor debug memory spam Message-ID: <473@glyph.UUCP> Date: 29 Jul 89 17:48:48 GMT References: <7408@ecsvax.UUCP> <3965@cps3xx.UUCP> <7413@ecsvax.UUCP> Reply-To: nichiren@glyph.UUCP (Andy Heffernan) Organization: Tiffany Fan Club Headquarters Lines: 22