I also have the same problem as Jules. Very annoying.

Me to, Sometimes when i break execution i have to step like said above and sometimes not. but it usually shows the script tab and tries to raise a dialog window that dont show upp (you can hear the sound), the test window is in a state that is running so logoff och break is impossible. only task manager can help me...

This has started to happen alot.
Shall i upload support info?
Using
Home: OraOdac11g_home1
DLL: C:\app\???\product\11.1.0\client_1\oci.dll
OCI: version 11.1
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0

I also have the same problem

I have tried the new version 8.0.4.1514 and now it is much better. When the debug is broken (shift-Esc), the system no longer hangs. A big thumbs up for the developers!

But (some people are never satisfied ;)): the execution is not stopped when the user breaks the debugger, the program continues to the end. Besides the potential great amount of time before the program comes to an end, there is a problem if the program communicates with external connections. For example a webservice, a mail-server or other non-transactional services, because this will cause for example a webservice to be called each time a program is tested, and test data may be destroyed because it is executed on a third party system.

A small test to verify this behaviour can be performed by executing a small piece of test code like the following:Enter debug mode and break the debugger at the line with NULL. The error "ORA-01476: divisor is equal to zero" is still shown, even if the debugger is broken before this line.

On Oracle 10g, the debugger is correctly broken as expected with the message "ORA-06543: PL/SQL: execution error - execution aborted"

Can this error be fixed for Oracle 11g as soon as possible?
Thanks...

Will this be fixed for 9.0?

We have not yet been able to reproduce this.

Hello Marco.

Which steps have you performed to reproduce?
Can you reproduce with the example code I reported in this topic on 19. June 2010?
The posters Jules, Jeff81, dragonsoft, Maxnet, datadeconline are all reporting the same issue, so it should not be too hard to reproduce.

It is critically important that this bug is locallised and fixed.

In our company we experience this problem on a daily basis, both by our inhouse developers and when we occasionally have to test code at our customers' databases.

The major problems are:
1) Sometimes PL/SQL developer hangs when a debug session is broken (Shift-Esc). When no database updates are done yet when stepping through the code, a break can usually be performed without problem, but when database updates are done, sometimes the debugger just hangs and sometimes the debugger asks if I want to break. I answer Yes, but the session is still in a strange mode where the red "execute lightning" is gone, but the green Run arrrow is still active in the test window. In this case, PL/SQL Developer can not be closed, because the debug session is reported as still running. The only way to quit PL/SQL Developer now is to use the task manager. When the debugger hangs after a database update, the Oracle session is still active with table locks etc. This session can be hard to kill and may at it's worst require a database restart to release the table locks by this session. So for customers where we have to test something, for instance to reproduce an error, this can be quite interfering for their work.

2) The debugger does not break execution when aquired, but continues the execution of code. This means, that if a method has table modifications with explicit commits etc., the data is changed. In the case of running test scripts in order to reproduce data errors etc. at customers, this can have adverse effects, as data can have been sent to other systems etc.

Please, please, please make an attempt to solve this problem.

If it can be of any help to you, I would be glad to participate in a shared dekstop session (for instance via Webex) where I can demonstrate the problem, and you or another developer/supporter can participate also. Please let me know, when this is convenient for you.

Hi Marco,

I follow all notes on before comment (Claus Pedersen), if I help to you please tell me. This is very important for us and for all PL/SQL developers.

Regards
PGuti

Hello, have you been able to reproduce?

It is a major problem.

Hello Marco, how is progress on this issue? My offer to participate in for instance a TeamViewer session or similar in order to illustrate the problems is still open ...

Not that I am counting, but is has been 774 days since the first post in this thread ...