Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re: Mystery Error
Message-ID: <8905031526.AA05629@richter.mit.edu>
Date: 3 May 89 15:26:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23

If I understand your C code (and I am not much of a C 
programmer), you are calling the main program recursively
with no ending condition. Each recursive call to the
program will "push" the return address of the call onto
the stack. Since there is no ending condition to the
recursive calls (ie. the subroutine calls never return),
the stack eventually gets completely filled with these
return addresses, and the stack overflows and trashes
something else (like maybe the program itself) for a
change. 

It's the same basic problem ... a program which writes
over itself destroys the debugging info along with
everything else.


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter@eddie.mit.edu
krowitz%richter@athena.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)