"Stop-Debugger" Problem

[JDietz]

Hi,

We have big problems to stop/break "test-window" sessions on 9.2.0.3 DBs using PL/SQL Developer 5.1.3.704.

Every time we try to stop debugging using the "break" button the "debug session" goes inactive but the "test session" remains active. The test window stays in "execution state", too. The "kill session" button on that "test windows" brings up an error message that the given SID does not exist. When I use the sessions window to kill that remaining "test window" an access violation window pops up after issuing the kill command - but it seems the process was killed. The PL/SQL Developer must be terminated after that error - maybe this is finally removing the "active" test window.

The last SQL Text of the "test window" is:
"declare ret binary_integer; begin ret := PBSDE.DEBUG_LOOP; end;"

On 8.1.7.4.1 we had this behavior sometimes but on 9.2.0.3 this happens everytime when we try to stop/break the debugger.

Any ideas?

Regards,
J. Dietz
Witron Integrated Logistics

 

[Marco Kalter]

Can you try the following?
[*] Create a new shortcut for PL/SQL Developer, with a DEBUG parameter on the command line. For example:

c:\program files\plsql developer\plsqldev.exe debug

[*] When the problem occurs again, immediately copy debug.txt from the PL/SQL Developer directory to a safe location.

[*] Send the debug.txt file to me.
[/list]

------------------
Marco Kalter
Allround Automations

[This message has been edited by mkalter (edited 10 September 2003).]

 

[JDietz]

Hi Marco!

I've sent you the "debug.txt" I've gotten after stopping & killing my debug session.

On 817 I rarly had to kill the remaining active "test window". Mostly both sessions the "debug" and the "test" session went inactive after pressing the break button.
9203 seems to bring some bugs with

Regards,
J

 

[JDietz]

On thing I'd like to add is that I am using the 8.1.7. client to reach our 9.2.0.x databases. Normally this shouldn't be an issue.