Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!brutus.cs.uiuc.edu!apple!genbank!agate!brahms.berkeley.edu!silverio
From: silverio@brahms.berkeley.edu (C J Silverio)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HELP! ID=01 on a Mac II
Message-ID: <1989Nov29.021049.25907@agate.berkeley.edu>
Date: 29 Nov 89 02:10:49 GMT
References: <1989Nov24.035604.27499@agate.berkeley.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: silverio@brahms.berkeley.edu.UUCP (C J Silverio)
Organization: Bath Department, UC Merkeley
Lines: 26

THANK YOU to Tim Maroney and Larry Rosenstein for their timely
comments. I now understand the "alignment" problem quite well, and
that my application was definitely not suffering from one.

I am still very mystified about what was causing the crash, since I
tested it originally on a MacII (regular) with 8Mb and single Finder
and NO inits. (I also scanned for virii, of which there were NONE.) We
suspect the motherboard of the MacII in question. This MacII has
recently (I just found out) been having Clock Problems. Of course the
service dude didn't find anything wrong with it.

The next day, I tried the SAME COPY of the program on the same hard
disk (ie. the one I hadn't bothered to chuck in the trash), and it
worked fine. 

So I put on the Heap Scrambler full blast, and turned on several
applications (Word with bkgd repage, etc) and could not crash it. I'll
have to get Discipline next.

SO I added a whole bunch more error checking code (at a 25% increase
in code size, and a 1% or 2% reduction in speed) and shrugged my
shoulders and delivered the puppy.

What other stress testing techniques do people recommend?

thanks for your help etc.