Path: utzoo!attcan!uunet!mcsun!sunic!uupsi!rpi!uwm.edu!cs.utexas.edu!tut.cis.ohio-state.edu!osu-20.ircc.ohio-state.edu!laufman-h
From: LAUFMAN-H@osu-20.ircc.ohio-state.edu (Harry Laufman)
Newsgroups: comp.lang.pascal
Subject: Juicy TP5.5 Problem
Keywords: TP5.5 problem
Message-ID: <12573366400018@osu-20.ircc.ohio-state.edu>
Date: 13 Mar 90 14:04:27 GMT
Sender: news@tut.cis.ohio-state.edu
Organization: The Ohio State University, Columbus, Ohio
Lines: 19

Regarding...> 8 Mar 90 15:13:28 GMT kam@itivax.iti.org (Keith A. McNabb)
> Juicy TP5.5 Problem
>Has anyone seen instances where Turbo Pascal 5.5 goes in the weeds
>just after entry to an overlaid unit?  I have pinpointed the spot
>of the crash, and the code is harmless and well tested.  Also,
>the location of the crash seems to depend on physical address, so
>that the crash occurs at different places when the code grows or
>shrinks.  If I place a debug message call at the spot, then the
>message produces strange results and the surrounding code works
>fine again.
 
Months ago I wrote a data analysis graphics package for our lab data
and had a similar problem.  The data didn't plot correctly.  I was using
two (w,x) out of four (w,x,y,z) parameters for a scatter plot, and the
program cycled, plotting (w,x), then (x,y), then (y,z) and so on.  In Debug
(Turbo's) things were fine.  If I added one line of code, either a debug
outtextxy('Values are...') or a pointless x:=x+1-1; program runs ok.  A
call to Borland and I was told to be sure to initialize ALL variables.
I did...problem solved.  Don't know exactly why.