Debugger woes on PL/SQL

[Martin Surasky]

I'm going through some pain points with the debugging functionality. I’m hoping someone has seen this in the past and maybe will be able to lead me in the right direction.

In a nutshell: even when compiling packages with debug info. I notice that, when I step into the code for SOME packages (not all of them) the variables show "(No debug information)"

Initially I discarded the lack of debug information and also miss/configurations at the server level as suspects of this. I can create a simple package on the same server and debug and get variable info just fine. It seems to be affecting some packages and not others.

Like I said, I can debug the offending package and even see the checkmark beside “Add debug information‿.

I even have checked the “Add debug information when compiling‿ (another reason to believe that this is not causing this problem).

Would anybody in this forum be able to think another obvious reason why this is happening to me?

Thanks!

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the PL/SQL Developer shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer 15\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the %APPDATA%\PLSQL Developer 15 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 15). Let me know the variable name that you tested during this debug session, so that we can find it in the log file.

 

[Martin Surasky]

Hi Marco!

Attached is the Debug.txt after running one slsqldev.exe with the DebugSQL parameter.

During that session I hovered over (and added to the Variables window...) a variable called "qty_arrived_inv_" so you can use that variable name (out of curiosity I peeked at the Debug.txt file to find a "GetVariable starts" for qty_arrived_inv_ so my activity is certainly tracked there)

Thanks again for your help!
View attachment Debug.txt

 

[Marco Kalter]

Thanks. Can you let me know what kind of varianle "qty_arrived_inv_" is? Is it a local variable in the function/procedure, a parameter, a global variable in the package body, or a global variable in the package specification? Can you also let me know the package name?

 

[Martin Surasky]

Hi Marco.

This variable in particular is a parameter, but I think the inability to watch variables is happening at the Package level. If you want, I can send you an email with the Package Body file (*.bdy) generated by PL/SQL Developer so you have the code at your disposal to investigate.

 

[Marco Kalter]

If you can send me the package specification and body, we can try to reproduce.

 

[Martin Surasky]

Will do!