I have a practice in which I clean the program for better understanding. In my other (this) OS I installed Netbeans 8.2. When debugging you are NOT supposed to debug everything in depth, but when you get to this part:
System.out.println("1.-sumar");
send me these codes of the image, and to continue debugging (giving the button) sends me more and more codes. How do I avoid this?
Use the F8 key to debug
Differences
Step Over ( F8 ) Executes a line of code. If the instruction is a method call, execute the method without entering the code of the method.
Step Into ( F7 ) Executes a line of code. If the instruction is a method call, it jumps to the method and continues execution by the first line of the method.
When that happens to me what I do is that I move the point from where debugging starts. Or it varied the way of purification.
With F7 the debugger "goes in" (step into) the code, instead with F8 causes the code to "go to the next (step over)".
F7 enter code shows the ins and outs of function calls and will deepen in it when many calls are made of functions that call others.
F8 On the other hand, going through it ignores the internal operation of function calls and only focuses on the value that returns.
If you need to debug a function called by the program, use the option "enter into" (step into). F7
But if you want to debug the current program, use the "move to the next" option (step over). F8
You can alternate the keys when debugging, you just have to do it at the right moment when you do it.
Imagine you are using F7 to debug (debugging - Step into) What you are doing is debugging even the internal functions that your code uses.
What you need is to only debug the program, for this use the key: F8 (Step over)