The issue you’re seeing is a “feature” of the DBMS Debugger. In an IDE like you would use for debugging C# or Java, the IDE itself keeps track of where exactly the execution code is. In Oracle, all of that information comes from the DB itself, not Toad. Every time you click on step in/over/out, Toad has to ask Oracle which line to go to next (you can see this if you click Database-> Spool SQL). What unchecking the “break on exception” does is prevent you from being prompted with the exception message that you would normally see. Since your code is actually going into the exception, it’s still an executable line of code and that’s why Oracle sends you there. Simply put, there isn’t any check/feature/option you can set to stop what you’re seeing.
Greg (formerly the debugger guy)
From: Kuvick1337 [mailto:bounce-Kuvick1337@toadworld.com]
Sent: Tuesday, March 29, 2016 7:06 AM
Subject: [Toad for Oracle - Discussion Forum] Debugging: step in to exception code (Break on Exception)
Debugging: step in to exception code (Break on Exception)
Thread created by Kuvick1337
I am facing the following situation:
I Have to debug a function which calls a lot of other functions which are exception based, heavily relying on the NO_DATA_FOUND to search somewhere else.
My function is about 300 lines of code but it takes like 700 clicks on “Trace Out” because every 2-3 lines the debugger jumps into an exception which may be deep down the callstack.
All of these are handled, no unhandled exception might occurr which could (and then should) crash the execution.
Is there any solution for this nuisance? I saw some older threads and topics from 2009 to 2011 but none of them gave a solution for this, they just covered the “Break on Exception” menu check box
which I have disabled anyway.
Thanks in advance,
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum
this post as spam/abuse.