Path: utzoo!attcan!uunet!decwrl!elroy.jpl.nasa.gov!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <26053@usc.edu>
Date: 20 Jul 90 04:30:35 GMT
References: <1500@faatcrl.UUCP> <25990@usc.edu> <1509@faatcrl.UUCP>
Sender: news@usc.edu
Distribution: na
Organization: Felsina Software, Los Angeles, CA
Lines: 24

In article <1509@faatcrl.UUCP> jprad@faatcrl.UUCP (Jack Radigan) writes:
>papa@pollux.usc.edu (Marco Papa) writes:
>>Stomping on location 0 is a no-no for any application program. This is 
>>usually the result of an uninitialized pointer.  I believe the hddisk
>>device (or whatever it is called) for the A590 and A2091 assumed that
>>nobody would stomp on location zero. I recall a message to that effect from
>>CATS people a while back.
>
>I'm aware of this already.  What is weird is that I can't duplicate it with
>ZeroMung on an A1000.  A simple dereferenced pointer can be found with this
>program, but not this semaphore guru.  It's truely bizzare.

Maybe I should have qualified 'stomping' as BOTH reading and writing 
location 0. On an A1000, ZeroMung & Co. will help you to find writing loc 0
problems.  No way for you to find 'reading loc 0' problems.

-- Marco




-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=