Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!mailrus.UUCP!markl%neptune.AMD.COM%amdcad%ames
From: markl%neptune.AMD.COM%amdcad%ames@mailrus.UUCP (Mark Luedtke)
Newsgroups: comp.sys.apollo
Subject: Re: Mystery Error
Message-ID: <8904271533.AA28250@neptune.AMD.COM>
Date: 27 Apr 89 15:33:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 9

Thanks for the clear explanation.  The thing that makes this a 'mystery
error' is that I have done these things before without that problem.  It
only occurs when the specific operation runs into the stack, which is not
common, but when it occurs, everything kills the stack (the old theory of
localization).  My program bug, found just as you mentioned, didn't take long
to find, it was just ugly, and repetative.  I'm sure there is some way Apollo
could handle this more elegantly.

Mark Luedtke    markl@neptune.amd.com    (512)462-5278