Sometimes standard breakpoints are not enough. Let's suppose you are processing a table with several thousands of records, and that the bug you are trying to fix always seem to appear on the second half of this process. Setting a breakpoint at the point where you are processing each record would not help in this situation, as you don't really want the debugger to stop on each record. At least not until half of those records have already been processed. And there is where awDebugger's conditional breakpoints come in your help.

awDebugger allows you to set a condition for each breakpoint, based either on the number of times the breakpoint has been hit, or on a condition that must be true when the breakpoint is reached, otherwise awDebugger will continue executing the application as if there were no breakpoints set at that line.

Just to name a few examples, by setting the appropriate conditions you can tell a breakpoint to interrupt the program's execution:

• Always (this would be the case for ordinary breakpoints)
• Only when the breakpoint was hit exactly n times
• When the breakpoint has been hit at least n times
• Every n times the breakpoint is hit
• Only if GlobalRequest = InsertRecord and ORD:Total >= 10000
• Only if ORD:Total >= 10000 and the breakpoint has already been hit at least 10 times