Path: utzoo!attcan!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!beach.cis.ufl.edu!dor
From: dor@beach.cis.ufl.edu (Douglas R. Oosting)
Newsgroups: comp.lang.pascal
Subject: Help with stack overflow
Keywords: turbo  error trapping  help   stack
Message-ID: <22863@uflorida.cis.ufl.EDU>
Date: 10 Apr 90 17:51:39 GMT
Sender: news@uflorida.cis.ufl.EDU
Reply-To: dor@beach.cis.ufl.edu (Douglas R. Oosting)
Followup-To: comp.lang.pascal
Distribution: comp
Organization: UF CIS Department
Lines: 21

I have a fairly large communications program in Turbo 5.0 which just 
(apparently) dumped with a stack overflow.  Ouch.  How can I trap something
like this?  I have the ExitPtr pointer set to a FAR routine {$F+} that
has no local variables (everything called in it is global to that unit)

Is there a kind soul out there who can help me?  I don't have a recursing
routine that should be causing this stack dump in the FIRST place...it would
help if I could trap it (the screen is cleared by the calling program so I
can't see the message given me by TURBO's exit code anyway...so I have *no*
idea where in the program this is happening...and the communications part
of the program keeps me from running the debugger on it...)

Thanks,
Doug 


--
And in the end/the love you take | Douglas R. Oosting, University of Florida
   is equal to/the love you make | dor@beach.cis.ufl.edu | dro@gnv.ifas.ufl.edu 
FNORD!--------The Earth is Our Mother, treat her with respect------------FNORD!
In the Society : Cadrys ap Dulas o Caereira, Barony of An Crosaire, Trimaris