Test window hangs the application

Jonas

Member
When I'm trying to debug some of my procedures PL/SQL Developer hangs. After starting the debugger, if I push the run button the procedure goes through, but if I push step into PL/SQL Developer hangs. Setting a break point in the procedure and push run also hangs the application.

Restarting PL/SQL Developer does not help. Recompiling the package/package body does not help. Adding debug information does not help.

PL/SQL Developer: 5.1.4.730
OS: Windows 2000
Oracle version: 9.2.0.4.0
 
Did all system views and packages compile correctly when installing these patches? In particular, can you recompile the debug packages by running $ORACLE_HOME/rdbms/admin/pbload.sql under the SYS account?
 
Hi Marco and Jonas

I'm experiencing the same kind of troubles. I've understood that sometimes I got into a loop when I added a breakpoint to a method of any package...
I have not understood yet if the recompilation
of the target packages is in any way involved as cause of the loop.
Unfortunately I have not yet any way to reproduce the malfunction.

> Is this database upgraded from a previous Oracle version?
In our case it is not. The DB was intalled brand new from scratch: v 8.1.7.4.0
PL/SQL Dev: v. 6.0.5.926

> In particular, can you recompile the debug
> packages by running
> $ORACLE_HOME/rdbms/admin/pbload.sql under the SYS account?
I've just asked to our DBA to recompile them
as indicated.
No problem reported: if useful I can provide
the log file that is clean.

Any hint?
Thanks in advance!

Cesare
 
If the Test Window hangs, it may be that the Oracle server process has died for some reason. Can you check if a trace file exist that is related to the problem, and if so, send it to me?
 
Marco
Yesterday before going home, the IDE hung up again
When I was back at office this morning
I got the usual exception report raised by PL/SQL
(I saved it as hardcopy/GIF image)
indicating the call stack and the exceptions that
were raised.
Moreover I retrieved the trace file dumped by the DB server (if it's "the trace" that can be of interest for you).

Please let me know how to forward you the GIF picture and the trace file (should I use the e-mail or via the forum?)

Thanks in advance
Cesare

P.S.
I have the feeling (it's not a certainty yet) that some problems are due to the disalignment between the "image" of a compilation unit (package, proc, funct...) that is loaded by the debugger/test window and the one that has been actually re-compiled.
Today I noticed that after having compiled a package, when the execution halted at a breakpoint
in that unit, the IDE displayed the source code exactly as BEFORE the changes.
Could it be interesting?
I apologize in advance if some remarks might be
naive or some terms not rigorous.
It's a quite short time that I work
to business software (and that I use PL/SQL Developer)
 
Originally posted by Marco Kalter:
To obtain some more diagnostic information, can you modify the PL/SQL Developer shortcut and add the debug parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debug
Hi Marco
Do you think it might work also when the debugger hangs?
The problem never lets up...

Bye
Cesare

P.S.
I will try for some days another IDE for PL/SQL to see if hanging up depends either on PL/SQL Developer or anything on the DB server...
 
Hi, Everyone! Hi, Marco!
For my mind pl/sql developer not hang up here.
At this time "test" session is waiting for pipe.
probably it waits message from "debug" session. Perhaps, there is some error in designing of the tandem between "test" and "debug" sessions but possibly may be some resource trouble in Oracle.
But, Marko, wanted hear your opinion
Thank for greate soft
 
These pbsde.debug_loop blocks are generated and executed by the Oracle Debug system (sys.dbms_debug package). It's very difficult to determine why this might hang for specific program units on specific configurations.
 
I noticed that, generally, having two or more test windows opened can worsen the problem.
I.e.: it happened that, when the IDE hung, closing the extra test window ublocked the situation
 
Back
Top