Hi gang I seem to be having problems with VFP9 (fully updated) debug. I think this has been a problem before but at the moment I find it often does not stop on a break point and I have to revert to set step on. Or the other way, it stops at placed I have no break point on. I have one debug I'm checking now and it stops twice during a scan which is fairly large and bloody annoying as I have to clear the break points to get it going again and lose the break point I want. Seems this time saver is taking more time than without. Does anyone else have this issue? Set moan off Al
On 14/01/2016 10:14, Allen Pollard wrote:
Hi gang I seem to be having problems with VFP9 (fully updated) debug. I think this has been a problem before but at the moment I find it often does not stop on a break point and I have to revert to set step on. Or the other way, it stops at placed I have no break point on. I have one debug I'm checking now and it stops twice during a scan which is fairly large and bloody annoying as I have to clear the break points to get it going again and lose the break point I want. Seems this time saver is taking more time than without. Does anyone else have this issue? Set moan off Al
When I get this happening I usually clear out all breakpoints, recompile, put the point back I want and it works. Occasionally I have to come out of fox and load up again.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
Hi Peter I came right out of foxpro after taking out all possible debug break points and watches. Deleting the foxuser and clearing the foxuser in options. Still does it. Exactly the same 2 places that do not have a watch or break point. As soon as I put a break point later in the code. Very odd.
Al
-----Original Message-----
When I get this happening I usually clear out all breakpoints, recompile, put the point back I want and it works. Occasionally I have to come out of fox and load up again.
Peter
Did you recompile? That's what I think the problem is: Fox using an old program version, so won't stop at the right place.
Peter Cushing IT Department WHISPERING SMITH
On 14/01/2016 10:45, Allen Pollard wrote:
Hi Peter I came right out of foxpro after taking out all possible debug break points and watches. Deleting the foxuser and clearing the foxuser in options. Still does it. Exactly the same 2 places that do not have a watch or break point. As soon as I put a break point later in the code. Very odd.
Al
-----Original Message-----
When I get this happening I usually clear out all breakpoints, recompile, put the point back I want and it works. Occasionally I have to come out of fox and load up again.
Peter
[excessive quoting removed by server]
1. Try deleting all fxp files, just in case. Recompilation does not always do the right thing.
2. Make sure there is no duplicate of your file being found El 14/01/2016 11:46, "Allen Pollard" profox@gatwicksoftware.com escribió:
Hi Peter I came right out of foxpro after taking out all possible debug break points and watches. Deleting the foxuser and clearing the foxuser in options. Still does it. Exactly the same 2 places that do not have a watch or break point. As soon as I put a break point later in the code. Very odd.
Al
-----Original Message-----
When I get this happening I usually clear out all breakpoints, recompile, put the point back I want and it works. Occasionally I have to come out of fox and load up again.
Peter
[excessive quoting removed by server]
Breakpoints you set in the code window are not updated correctly if you add/remove code before the location where the breakpoint is set. That's why you get it seemingly stopping at places where you don't actually have a breakpoint set, or not stopping where you think you have a breakpoint set.
Fred
On Thu, Jan 14, 2016 at 3:14 AM, Allen Pollard profox@gatwicksoftware.com wrote:
Hi gang I seem to be having problems with VFP9 (fully updated) debug. I think this has been a problem before but at the moment I find it often does not stop on a break point and I have to revert to set step on. Or the other way, it stops at placed I have no break point on. I have one debug I'm checking now and it stops twice during a scan which is fairly large and bloody annoying as I have to clear the break points to get it going again and lose the break point I want. Seems this time saver is taking more time than without. Does anyone else have this issue? Set moan off Al
[excessive quoting removed by server]
Thanks everyone for the answers. I closed VFP, deleted the fxp files and recompiled. Seems to have done the trick. Al
-----Original Message-----
Breakpoints you set in the code window are not updated correctly if you add/remove code before the location where the breakpoint is set. That's why you get it seemingly stopping at places where you don't actually have a breakpoint set, or not stopping where you think you have a breakpoint set.
-
Allen Pollard -
Fernando D. Bozzo -
Fred Taylor -
Peter Cushing