Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link Par2: Debugger -- Conditional Breakpoint 1999-03-11 -- Russ Eggen The debuggers do not support conditional breakpoints at this time. I have
asked for this myself (it would be a great feature!).
However, I have found a way to make my conditional breakpoints: code them
yourself. Here is how I do it:
If SomeBreakCondition
x# = MeaninglessValue
END
This code is harmless, but if you set your breakpoint on the
MeaninglessValue line, then when that condition occurs, it executes and the
debugger regains focus and you can now inspect your variables. Of course,
you have to place this code as close as possible to where you think the code
is breaking. You can use as many of these as you wish.
I used this method after some long searching to find out why a conversion
program failed on a large file. I wanted to find out why record number
400,385 was causing the program to behave incorrectly. I certainly had no
need to debug all the process loops 400,384 times!
Today is November 21, 2024, 7:07 am This article has been viewed 35197 times.
|
|