Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Ilya Rabyy
  Where is Ilya Rabyy?
 Fountain Valley
 California - United States
 Ilya Rabyy
 To: Ken Murphy
  Where is Ken Murphy?
 Springhill
 Canada
 Ken Murphy
 Tags
Subject: RE: Prog stops where it shan't in Debugger
Thread ID: 154927 Message ID: 154936 # Views: 1 # Ratings: 0
Version: Visual FoxPro 9 Category: Errors & Debugging
Date: Thursday, December 20, 2007 5:57:20 PM         
   


> > Colleagues,
> >
> > I thought I've seen it all (well, almost) but this...
> >
> > I am debugging a method in a class someone else has programmed a while ago and I have now modified;
> >
> > I put SET STEP ON before a SCAN cycle in the code and ran the code;
> >
> > Execution stopped where it's supposed, and I continued with step-by-step execution in the Debugger;
> >
> > 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?
> >
> > TIA!
> >
> > Regards,
> >
> > Ilya
>
> Ilya,
>
> Never seen this behaviour. Just a SWAG, but could there still be a breakpoint sitting in the code in the parent class? One would think that it should show you that parent class code in your debugger, but ...
>
> Ken
> You shall know the truth - and the truth shall set you free. (John 8:33)

Nope, no executable code in the parent class's code (just comments on how to implement it). And it stops before going into execution of a function (actually - stand-alone PRG) whenever there's SET STEP ON statement in the code; if it ain't there - it doesn't stop and works as it should (save for the glitch I'm trying to catch - hence debug mode).

Regards,

Ilya

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