1320 Visual Studio .NET Debugger Appendix D Disabled (Free web hosting services)
1320 Visual Studio .NET Debugger Appendix D Disabled breakpoint Fig. D.12 Fig. D.12Fig. D.FiFi12g. D.12g. D.12Disabled breakpoint. Testing and Debugging Tip D.6 Disabled breakpoints allow the programmer to maintain breakpoints in key locations in the program so they can be reactivated when needed. Disabled breakpoints are always visible. In the Breakpoints window (Fig. D.11), the Condition field displays the condition that must be satisfied to suspend program execution at that breakpoint. The Hit Count field displays the number of times the debugger has stopped at each breakpoint. Double-clicking an item in the Breakpoints window moves the cursor to the line containing that breakpoint. A programmer can add breakpoints to a program by clicking the New button in the Breakpoints window. This causes a New Breakpoint dialog to display (Fig. D.13). The Function, File, Address and Data tabs allow the programmer to suspend execution at either a method, a line in a particular file, an instruction in memory or when the value of a variable changes. The Hit Count… button (Fig. D.14) can be used to specify when the breakpoint should suspend the program (the default is to alwaysbreak). A breakpoint can be set to suspend the program when the hit count reaches a specific number, when the hit count is a multiple of a number or is greater than or equal to a specific number. The Visual Studio debugger also allows execution to suspend at a breakpoint depending on the value of an expression. Clicking the Condition button opens the Breakpoint Condition dialog (Fig. D.15). The Condition checkbox indicates whether breakpoint conditions are enabled. The radio buttons determine how the expression in the text box is evaluated. The is true radio button pauses execution at the breakpoint whenever the expression is true. The has changed radio button causes program execution to suspend when it first encounters the breakpoint and again each time the expression differs from its previous value when the breakpoint is encountered. When the New Breakpoint dialog has been closed, the Breakpoints window displays the condition and hit count options for the new break point. Suppose we set x*i!=0 as the condition for the breakpoint in our loop, with the has changed option enabled. (We might choose to do this because the program produces an incorrect output of 0). Program execution suspends when it first reaches the breakpoint and records that the expression has a value of true, because x*i is 100 (or 10 if we fixed the earlier logic error). We continue, and the loop decrements i. While iis between 10 and 1, the condition s value never changes, and execution is not suspended at that breakpoint. When iis 0, the expression x*i!=0is false, and execution is suspended. At this point, the programmer identifies the second logic error in our program the final iteration of the forloop multiplies the result by 0. To return the IDE to design mode, click the Stop Debugging button on the Debug toolbar.
We recommend high quality webhost to host and run your jsp application: christian web host services.