Here's the scenario: I have introduced a break point at the beginning of a method that I want to debug ... first say That's the part 1 in this method that I want to step up / move in some codes ... well ... there is a loop after where I'm not interested in stepping in on /, I just want to debugger Tell me, you've run this loop for yourself 10 times and just let me know in part 2 of my code. Let not that starts after this loop, it is possible to do with debugging options?
Then something like this:
Breakpoint: Mymouth {Part One of the Part Code: OK, Debug it, while Loop: I do not care, Debugging it Do not want to part two of the code: yes, I want to debug it too)
Right-click on the line of the code to run, and click on "Run-to-Cursor", or you can set a second breakpoint after the loop and just run.
Edit: How did you ask two questions? The above method will allow you to proceed on the entire loop, even if it happens with many iterations. If you want to go through the loop body only 10 times, then add a breakpoint on the last statement of the loop, right-click on that line, click on "Breakpoint", then click on "Hit Gate" Then "Break when hit count is the same" and put 10 in the box that appears, it will stop the program after executing the loop 10 times (you have to manually change the current statement), but Gar loop less than 10 times (when I add an extra breakpoint after the above suggestions loop) does not break down.
Comments
Post a Comment