LINE POINTER IN DEBUG MISBEHAVES

[IlyaRabyy]

Colleagues,

That sometimes the record pointer in Debugger stops at the code's line before the stop point (e.g. SET STEP ON) is a well known fact.
However, I haven't seen this pointer shown "stopped" at a code's line way down after the stop point!.. That is - until now. :-(
In my case, I have SET STEP ON, say, on line #100, and the Debugger does stop the execution at that line, but it shows the line pointer stopped at the line #, say, 450...
This always happens after the execution passes CREATE CURSOR command (somewhat lengthy this one, 45 lines in the code).
If you ask how I know that the Debugger has actually stopped where it's supposed to, it is by checking the contents of the memvars whose values are assigned in the code below that my stop point.

Have anyone encountered such faulty behavior of Debugger, and what can be done to fix it?

AHWBGA!


Regards,

Ilya

 

[Mike Lewis]

I just SET RESOURCE OFF and created a breakpoint in a new PRG file. It doesn't show up in Foxuser, but it works.

The breakpoint might work in the current session, but if you have SET RESOURCE OFF, it will not be stored anywhere. If you exit VFP, then go back in, your breakpoint will no longer be there.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[Olaf Doschke]

Yes, Mike, that's how it is.

And "unfortunately" there also is no phantom breakpoint remaining in the PRG (or FXP).
Well, and it's not surprising the breakpoint also is in memory to work, every other place would be too slow to access.

Bye, Olaf.