A breakpoint is a trigger in a program that, when reached, pauses program execution allowing you to examine the values of some or all of the program variables. By setting breakpoints in potential problem areas of your source code, you can run your program until its execution reaches a location you want to debug. When your program execution encounters a breakpoint, the program pauses, and the debugger displays the line containing the breakpoint in the Code Editor. You can then use the debugger to view the state of your program. Breakpoints are flexible in that they can be set before you begin a program run or at any time while you are debugging.
Breakpoints set on comment lines, blank lines, declarations, and other non-executable lines of code are invalid and will not be verified by the debugger.
The JDeveloper debugger supports a number of different types of breakpoints:
Deadlock breakpoints are useful in situations when you find it difficult to locate the source of the deadlock. When a deadlock breakpoint is encountered, the debugger halts. The deadlock breakpoint is automatically enabled when you start debugging.
Note: Breakpoints set in an a Java class or PL/SQL procedure will propagate to another having the same fully-qualified name. The classes or procedures can belong to different projects or connections. The propagation is by line number: if the two files are not identical, the positions of breakpoints in the second will be effectively random.
Information about set breakpoints can be viewed in the Breakpoints window. For more information about this window including its context menu options, press F1 or click Help in the Breakpoints window.
To open the Breakpoints window which displays a list of set breakpoints:
To change which columns are displayed in the Breakpoints window:
Copyright © 1997, 2004, Oracle. All rights reserved.