About Debugging a Stored Program Unit

All debugging actions, such as creating breakpoints, stepping through code and examining or modifying local variables, can be done directly on stored PL/SQL program units and packages. However, you cannot set breakpoints in database triggers.

The stored program unit may or may not be created with the debug information. To create stored program units with debug information, do one of the following:

Otherwise, if a stored program unit is compiled with no debug information, expect the following behavior during debugging:

Restrictions

When using the debugger across different machines to debug FMX and FMB files, the target files that are to be debugged must be regenerated on the target machine if you move them.

For example, if you have an FMB and an FMX that are generated on machine A, and you copy them over to machine B, and if your client debugger is on machine C, any breakpoints that you set on the files on machine B will be ignored by the debugger. You will need to regenerate the files on machine B in order for the client debugger on machine C to see the breakpoints.


About Breakpoints and Executable Source Lines

About Debugging a PL/SQL Library

Creating a Breakpoint