This content has been marked as final. Show 4 replies
It is possible the breakpoints aren't on code lines - sometimes the apparent line numbers are wrong. Try bracketting a line with breakpoints on either side.
Following your suggestion, I put break point on 6 lines following the DBMS_DEBUG_JDWP.CONNECT_TCP call.
3 of those lines are code lines. I also have 2 break points on code lines in a procedure being called at one of those 6 lines.
I have no problem hitting those stops if I 'Run as Debug'... but they are ignored when doing the remote debug.
In the remote debug session I do see all the break points lists in the Breakpoints tab. I'm very confused.....
An experiment -
Tools > Preferences > Debugger
Start Debugging Option:
- Step Over
Try this. This allows you to start a debug session sans breakpoints. You can then step over or into your code once the debugger session 'attaches.' I believe this will work for remote...
Good suggestion, but I already had that debugger property set.
I got it working! What I didn't realize was that you need to be logged into the database with the same credentials in both the local and remote session. I was trying to debug as the package owner and executing the procedure using our 'web' runtime user id.......
I learned that the break points are userid specific.
Thanks for all your great suggestions!