Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: suhas hegde
  Where is suhas hegde?
 sirsi
 India
 suhas hegde
 To: Tamar Granor
  Where is Tamar Granor?
 Elkins Park
 Pennsylvania - United States
 Tamar Granor
 Tags
Subject: RE: Prog stops where it shan't in Debugger
Thread ID: 154927 Message ID: 155002 # Views: 1 # Ratings: 0
Version: Visual FoxPro 9 Category: Errors & Debugging
Date: Friday, December 21, 2007 12:23:39 PM         
   


> > After going through a dozen of iterations, I set the blinker (cursor) at the statement after the ENDSCAN and clicked "Run to cursor" button at the top;
> >
> > The execution stopped in the middle of the cycle instead;
> >
> > I set the blinker at the same statement after the ENDSCAN and clicked "Run to cursor" button again;
> >
> > The execution stopped in the middle of the cycle again, at that same statement as it did the first time;
> >
> > After repeating the two steps above - with the same effect - I set the breakpoint (red dot) at the very last statement in the method and clicked the Resume button;
> >
> > The execution stopped in the middle of the cycle again, at that same statement as it did the first time... on the line with
> >
> >
m.SomeMemVar = SomeFunction(Param1, Param2)

> > I checked the code in this function and found nothing that might varrant such behavior.
> >
> > I even checked the Breakepoints "cheat sheet" and made sure nothing's there - still the same behavior!
> >
> > Apparently, there's something that causes such behavior!
> >
> > Where do I look to find the cause?
>
> Wish I had a solution. I have one just like this--one place in code where if I'm tracing, I get a break without a breakpoint.
>
> Since I never use SET STEP ON, I'm confident that's not involved.
>
> The spot where this happens is, I think, a place where I once had a breakpoint, but I've long since cleared it. I haven't tried renaming FoxUser.DBF, but I suspect that would do it.
>
> Tamar

Hi,
I checked and and the break points are stored in the resource file.

Suhashegde

ENTIRE THREAD

Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/20/2007 5:13:21 PM
RE: Prog stops where it shan't in Debugger Posted by Ken Murphy @ 12/20/2007 5:17:47 PM
RE: Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/20/2007 5:57:20 PM
RE: Prog stops where it shan't in Debugger Posted by Jon Goad @ 12/20/2007 5:26:47 PM
RE: Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/20/2007 5:50:51 PM
RE: Prog stops where it shan't in Debugger Posted by suhas hegde @ 12/20/2007 6:55:02 PM
RE: Prog stops where it shan't in Debugger Posted by Tamar Granor @ 12/20/2007 10:32:40 PM
RE: Prog stops where it shan't in Debugger Posted by suhas hegde @ 12/21/2007 12:23:39 PM
RE: Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/21/2007 5:11:49 PM
RE: Prog stops where it shan't in Debugger Posted by suhas hegde @ 12/21/2007 6:20:02 PM