![]() ![]() #JREBEL DEBUG UPDATE#>Update ‘Tech’ application (Ctrl + F5): update program, which can be executed after your code is changed. ![]() >Rerun ‘xxxxx’: rerun the program, which will shut down the service and restart the program. The second group of buttons, a total of 7 buttons, from top to bottom in order as follows: >Evaluate expression (ALT + F8): evaluate expression, which will be explained in detail in later chapters.Ģ. >Run to cursor (ALT + F9): run to the cursor, you can position the cursor to the line you want to view, and then use this function, the code will run to the cursor line, without breaking the point. >Drop frame (default none): fallback breakpoint, which will be explained in detail in later chapters. At this time, the method has been executed, but the assignment has not been completed. >Step out (Shift + F8): step out, exit from the entered method to the method call. You can use this method to enter the official class library when viewing the underlying source code. >Force step into (ALT + Shift + F7): you can enter any method by force. It is generally used to enter the user-defined method, but not the method in the official class library, such as the put method in line 25. If there is a method in the current line, you can enter the method. If there is a method on this line, it will not enter the method. >Step over (F8): step over and go down line by line. >Show execution point (ALT + F10): if your cursor is on another line or page, click this button to jump to the current line of code execution. First of all, the first group of buttons, a total of 8 buttons, from left to right in order as follows: The function of debug mainly corresponds to two groups of buttons 4 and 5 in Figure 1ġ. : in the menu bar run, you can debug the corresponding function and view the corresponding shortcut keys. : if there is no toolbar or status bar at the bottom of your idea, you can open it in view to display the toolbar, which will be convenient for us to use. : check show debug window on breakpoint in the settings, and the debug window will be activated automatically after entering the breakpoint ⑧ Watches: to view variables, you can drag the variables in the variables area to watches ⑦ Variables: in the variables area, you can view the variables in the current method before the current breakpoint. If you check the button in the upper right corner, the methods of other class libraries will not be displayed, otherwise there will be a lot of methods. ⑥ Method call stack: all the methods that the thread has been debugged are displayed here. ⑤ Service button: you can close / start services, set breakpoints, etc. The same corresponding function can be found in the menu bar run, as shown in Figure 1.4. Hover over the buttons to view the corresponding shortcut keys. The main function of debugging corresponds to these buttons. ④ Debug button: there are 8 buttons in total. If it is not activated automatically, you can set it in settings, as shown in Figure 1.2. ③ Debug window: after the access request reaches the first breakpoint, the debug window will be activated automatically. ![]() The color of the breakpoint line can be set by yourself. ② Breakpoint: left click in the left line number bar, or press the shortcut key Ctrl + F8 to open / cancel the breakpoint. In development, I usually start debug mode directly to debug code at any time. ① Start the service in debug mode, and the button on the left starts in run mode. Let’s talk about the eight points in the figure below #JREBEL DEBUG MAC#I’m here for windows, which may be different from Mac icons. The following is the interface after starting debug mode in idea and entering breakpoint. #JREBEL DEBUG HOW TO#So learn how to use debug in IntelliJ idea, mainly including the following contents:ġ0、 Attachment: jrebel activation 1、 Debug beginsįirst, take a look at the interface in debug mode in idea. Usually, we can also enable debug mode to track the running process of the code to learn the source code of the tripartite framework. Enabling debug mode can analyze and locate the location of the exception and the change of parameters in the running process. ![]() Usually, there are exceptions in the running process of the program. Debug is used to track the running process of the code. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |