Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!emory!hubcap!ncrcae!usceast!yarnall
From: yarnall@usceast.UUCP (Ken Yarnall)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Summary: How many bytes to clear??
Message-ID: <3344@usceast.UUCP>
Date: 19 Jul 90 17:23:44 GMT
References: <31705@cup.portal.com> <619@cbnewsb.ATT.COM> <3339@usceast.UUCP> <12378@netcom.UUCP>
Distribution: na
Organization: Math Department, University of South Carolina (ahem; The USC)
Lines: 31

In article <12378@netcom.UUCP> mcmahan@netcom.UUCP (Dave Mc Mahan) writes:
+
+ In a previous article, yarnall@usceast.UUCP (Ken Yarnall) writes:
+>In article <619@cbnewsb.ATT.COM> mab@druwy.ATT.COM (Alan Bland) writes:
+>+
+>Well, I have not called Jack's BBS, but The copies of JRcomm I have had
+>contact with (A friend has a registered copy of 1.0, and I have a
+>distribution copy through him) both crashed quickly on machines equipped with
+>a 2091.  By running a tiny little program I wrote to clear location zero, the
+>problem goes bye-bye.  Being careful with those nasty NULL pointers?
+
+Did you clear JUST location 0, or did you clear the 4 lowest bytes?

I cleared the long word that starts at location 0.  Here:

main() {
    long *p;

    p = (long*) 0L;
    *p = 0L;
}

It works for me...

+  -dave

kenny
-- 
         Ken Yarnall                 ///   yarnall@cs.scarolina.EDU
          Math Department, USC   \\\///   yarnall@ucseast.UUCP
           Columbia, S.C. 29208   \\\/   (803)777-6686