.java files can be debugged at breakpoints in the development environment, and.jsp files can also be debugged at breakpoints. But.jsp files add breakpoints in a different way than.java files..jsp adds debugger to the code to be debugged. Statement to identify the location of the breakpoint, and when the current page click triggers the code, the browser’s F12 debug interface will automatically pop up a debugging message. \

Type before mistakesdebugger, the process will get stuck, check for errors.



After an event is clicked, the F12 debugging page of Chrome automatically displays debugging information. The debug button is located in the upper right corner of the Sources debug window, and its functions and positions are shown in the following figures.

Shortcut key F8, if there are multiple breakpoints, click to directly enter the next breakpoint, ignore all the logic inside the breakpoint.

Function 2 – Ignore the internal implementation of the code and proceed to the next method:.

Shortcut F10, ignore the internal logic of the method, click to jump directly to the next method of the current breakpoint.

Function 3 – Step by step debugging, line by line:

Shortcut F11, in code order, from top to bottom, line by line.

Function 4 – Jump out of the current function and proceed to the next step

Shortcut key Shift +F11.

4. Compatibility:

I know supportdebugger;Some browsers may not be suitable for breaking point debugging, but as developers are usually based on Google Chrome debugging: