1.debug, all print
2. Before break point debug, single-step debugging, etc. buttons appear, run only breakpoint
3.setup over a line of code debugging
All break the code running behind 4.setup out
5.debug debug window display button
6. The operation point corresponding to the variable value is displayed
7.step into: single stepping, and continues to encounter Functions entered single-step (in short, to enter the sub-function);
step over: When single-stepping, will not enter the subroutine encountered in the single step function in the sub-function, but will then stop executing the entire sub-function, that is, the entire sub-functions as a step. One thing, through our simple debugging, in the absence of Functions and step into effect is the same (in short, over the subroutine, but sub-function performs).
step out: when stepping into the subroutine, step out can be completed by performing the remainder of the subroutine, and returns to the function level.
Press shift + F9 to enter debug
Run to c = add (a, b), click into the subroutine step into
One way: step by step point step into finished running subroutine then jump back to the main function Functions
The second way, a one-time point after executing step out of all sub-functions to add the step jump subroutine main function
step into my code and step into the measured seemingly nothing different, are met Functions to enter the Functions which go step by step execution, jump out of the implementation of the main function.
Great God who know the difference between hope the wing.
run to cusor measured variable is cleared debugging information, feel futile, the god who want to know the difference between the wing.
---------------------
Author: test_sharing
Source: CSDN
Original: https: //blog.csdn.net/jpmsdn/article/details/81025558
Disclaimer: This article as a blogger original article, reproduced, please attach Bowen link!