Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!ccut!titcca!kddlab!atrpost!atr-la!alain
From: alain@atr-la.atr.co.jp (Alain de Cheveigne)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock
Message-ID: <3872@atr-la.atr.co.jp>
Date: 21 Dec 89 02:01:29 GMT
References: <1989Dec19.091303.13316@agate.berkeley.edu> <3373@hub.UUCP <5896@internal.Apple.COM>
Organization: ATR International,Japan
Lines: 19
In-reply-to: chewy@apple.com's message of 20 Dec 89 18:00:06 GMT


in article <5896@internal.Apple.COM>$@$G(Jchewy@apple.com (Paul Snively) says:

>Another good thing to do is to have some utility (a debugger or an INIT) 
>that stuffs address zero with some magical longword that's guaranteed to 
>cause a Bus Error if accessed on any machine.  It's useful for tracking 
>down those intermitent NIL-handle/pointer references.

My own Christmas wish is a program that you could run under MF with
the program you're debugging, and that would allocate all the
remaining memory and check it for over-writing.

The idea that a bug from my program might be walking all over another
program's memory space (or vice-versa) is unnerving.



Alain de Cheveigne,
alain@atr-la.atr.co.jp