Skip to Main Content
Forums

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Remote Debugger - Breakpoints ignored?

311747Feb 8 2013 — edited Feb 11 2013
I am trying to remote debug a package using SQL Developer.

I've added the following line to the package:
DBMS_DEBUG_JDWP.CONNECT_TCP( '132.123.123.123', 4000 );
Compile for debug
add some break points.
I start a Debug Listener on port 4000.
Then call the procedure from another session.

A debugger session opens up in SQL Developer, but the procedure never stops at any of the break points. It simply runs to the completion w/o stopping.

There is a debugger window w/ the following message:
Debugger accepted connection from database on port 4000.

but no stack. The procedure finished normally.

Has anyone else seen where the breakpoints are ignored in a remote debugger session?
Thanks much!

Versions info:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Oracle SQL Developer (3.2.20.09)

Comments

Jim Smith
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.
311747
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...
311747
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!
1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Mar 11 2013
Added on Feb 8 2013
#plsql, #sql-developer, #sqldeveloper
4 comments
1,142 views