When trying to debug and walk through the code, none of the line numbers line up.
Executable line delimiters (blue dots) are not noting actual executable lines.
When tracing through, the debugger will stop at the wrong lines. If there is a break point set, the debugger stops at the wrong line.
Stepping though the code, the cursor may stop at white space or comments and skip legitimate lines of code.
None of the variable watches show data. If I watch a string, the value is not null, not an empty string, or a valid value, it is simply "blank" with nothing there.
Newline, comments between the "Create or Replace Function" command and the function title throws off executable line recognition in Toad's debugger.
Ex:
CREATE OR REPLACE FUNCTION
/*
Newline and/or some comments here
*/
CCHIU.TESTING_DEBUGGING
WORKAROUND:
Do not have newline or comments between the "Create or Replace Function" command and the function title. Have both pieces on the same line.
Ex:
CREATE OR REPLACE FUNCTION CCHIU.TESTING_DEBUGGING
/*
Newline and/or some comments here
*/
STATUS:
Issue fixed in version 9.0. The latest version of Toad for Oracle can be downloaded here.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center