Short: Debug tool for pool-allocations, a la Mungwall (OS3.x) Author: Magne Oestlyngen (magneo@stud.cs.uit.no) Uploader: Magne Oestlyngen (magneoe@stud.cs.uit.no) Type: dev/debug ------------------==================================------------------ 950527 PoolWatch release 1.02 Requires AmigaDOS 3.0 (V39) or higher to run. Copyright © 1994-1995 Ultima Thule Software All Rights Reserved. Author: Magne Østlyngen ------------------==================================------------------ Disclaimer ~~~~~~~~~~ This software entitled "PoolWatch" is not public domain but freely distributable (FreeWare). This means that you can copy it and give it to all your friends, upload it to a BBS or include it in a PD-library. The only restrictions are: All the files included in this archive must be in their original form without additions, deletions or modifications of any kind. PoolWatch may not be distributed for profit, and only a nominal charge may be associated with its distribution. Permission is hereby given to distribute PoolWatch on the Fish disks (CD or floppy) and the AmiNet CD. If you want to distribute "PoolWatch" with any commercial product, you will need written permission from the author. "PoolWatch" is provided "AS IS" without warranty of any kind, and the author is not responsible for any damage this software may do. (Just in case :-) What is PoolWatch ? ~~~~~~~~~~~~~~~~~~~ PoolWatch is a debug tool for OS 3.0 and higher designed to watch and correct illegal allocation and freeing of memory that use the pool-functions provided in OS 3.0 and upwards. PoolWatch is necessary since Mungwall do not catch any illegal memory handling concerning pool-allocations. PoolWatch is especially useful in combination with Enforcer, Mungwall (which will watch normal allocations that use AllocMem/FreeMem), SegTracker and FindHit (included in the Enforcer archive). If SegTracker is running in the system when PoolWatch is started, PoolWatch will use the public SegTracker seglist tracking for identifying the hunk and offset into the executable doing illegal allocations. What does PoolWatch do ? ~~~~~~~~~~~~~~~~~~~~~~~~ PoolWatch will patch CreatePool(), DeletePool(), AllocPooled(), and FreePooled() in exec.library. PoolWatch will use these functions but will add extra security on top of all pool-allocations. In most cases of illegal allocation/freeing, PoolWatch will report the error to the user and correct the problem (if possible). Please note that PoolWatch does not offer any memory protection if a task writes to a random addresse in memory, but will take care of most problems associated with pool allocations. ============================= Archive contents ============================= Original Packed Ratio Date Time Name -------- ------- ----- --------- -------- ------------- 6772 3689 45.5% 27-May-95 22:48:54 +poolwatch 9042 3480 61.5% 27-May-95 22:56:18 +PoolWatch.doc 2871 1288 55.1% 27-May-95 22:59:44 +poolwatch.readme 130 98 24.6% 05-Apr-95 19:15:58 +SCOPTIONS 1304 685 47.4% 05-Apr-95 18:13:54 +test 975 403 58.6% 05-Apr-95 19:16:30 +test.c -------- ------- ----- --------- -------- 21094 9643 54.2% 29-May-95 10:34:18 6 files