PL/SQL Developer Debugger

[Rick Silvers]

To all,

How do you stop the debugger when you encounter an error ?
I have tried using STEP OUT (CTRL T) and BREAK (SHIFT+ESC) and neither
works.
It's like the debugger gets caught in a loop and will not stop, I still see
Executing at the bottom of the screen. I usually
have to ALT+CTL+DEL and bring up Windows Task manager and click PL/SQL
developer and then click
End Task.

Is there a bug in the debugger or is there a parameter I'm not setting ?
Several other developers have complained about the
same issue . . .

I'm running Win XP professional on a HP 883n and telecommuting thru Secure
Client VPN.

Thanks,
Rick

 

[Marco Kalter]

What kind of error do you encounter? If this is an unhandled SQL or PL/SQL exception, then the debugger should finish immediately.

 

[Cesare Zecca]

Originally posted by Rick Silvers:
To all,

How do you stop the debugger when you encounter an error ?
I have tried using STEP OUT (CTRL T) and BREAK (SHIFT+ESC) and neither
works.
It's like the debugger gets caught in a loop and will not stop, I still see
Executing at the bottom of the screen

[...]

Hi Rick
That description remembers me the same type of problems we have...
(cf. Test window hangs the application
http://www.allroundautomations.com/ubb/ultimatebb.php?ubb=get_topic;f=3;t=000859#000000
)
Unfortunately, after many occurrences of the inconvenient I have no idea yet about any way to reproduce it.
I suspect that it's related to a mix of
recompilation dependencies & times, breakpoint handling.
Some weeks ago I began to suspect utPLSQL, but currently it happens also when we work with no interaction with that unit testing framework.

Bye
Cesare

 

[Ivan C.]

Greetings guys.
We've been taking care of this problem in numerous occasions, so we know what the problem is. Here's the scenario, and I hope it's exactly as in your case:
We'd start debugging in a test window and at the point of entering the module (procedure, function) from the anonymous block PL/SQL would hang...
I immediately go to our DBA and request an increase of the shared pool size. Usually 100 - 200 MB should be enough. Also, make sure you don't go over your maximum SGA size when increasing the shared pool.
Once that's done, everything works, and we're back in business...

I hope this helps.
Regards,
Ivan C.

 

[Albert]

Hi, Everyone! Hi, Marco!
First of all. Thank for greate soft!
This porblem realy exists.
At this time "test" session is waiting for pipe.
It happens to kill this session.