Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!samsung!zaphod.mps.ohio-state.edu!sunybcs!boulder!streich
From: streich@boulder.Colorado.EDU (Mark Streich)
Newsgroups: comp.lang.pascal
Subject: Re: Mouse support for Turbo Pascal 5.5
Message-ID: <23744@boulder.Colorado.EDU>
Date: 20 Jul 90 20:45:20 GMT
References: <90197.213141EX0@psuvm.psu.edu> <1990Jul18.055406.17988@uwasa.fi> <17165@dime.cs.umass.edu>
Sender: news@boulder.Colorado.EDU
Reply-To: streich@boulder.Colorado.EDU (Mark Streich)
Organization: University of Colorado, Boulder
Lines: 21

In article <17165@dime.cs.umass.edu> eli@smectos.CS.UMASS.EDU (Eli Brandt) writes:
>program BugTest;
>{
>Demonstrates a bug in the integrated debugger in TP 5.5
>
[... stuff deleted ...]
>procedure ReceiveVec(v1: vec3);            { or "var v1: vec3" to fix       }
>begin                                      { <-- run to this line      ***  }
>  writeln(v1.x, ' ', v1.y, ' ', v1.z);
>end;

When you tell the debugger to run to that line, you are actually running to
a point that is not yet in the procedure (i.e., the stack frame has not been
correctly set yet).  If you step into the procedure one more line, you will
see the correct values because the frame pointer has been set correctly by
that time.

Let's not accuse a vendor of "bugs" without a little more thought, OK?

Mark Streich
streich@tigger.colorado.edu