| PL/SQL Developer Debugging Hangs [message #325557] |
Fri, 06 June 2008 10:12  |
pmcginnis
Messages: 2
Registered: June 2008
|
Junior Member |
|
|
PL/SQL Developer Debugging constantly hands when I got to start the debugger and never comes back. Then other times it doesn't. I noticed if I view package/body, recompiled and added debug info 3-4 times, it works, but again, other times it still hangs.
Any help would be greatly appreciated!
Thank You.
|
|
|
|
| Re: PL/SQL Developer Debugging Hangs [message #325565 is a reply to message #325557] |
Fri, 06 June 2008 10:22  |
 |
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
|
Senior Member |
|
|
I suspect that the annoying symptom ("hang") has nothing to do with Developer itself.
Let us say you have a procedure which does some DML & it gets invoked.
Further this procedure does NOT contain any COMMIT.
Now image in a different window or session try to (re)compile this procedure.
This session will quietly wait until the 1st session issues a COMMIT or ROLLBACK to ensure data integrity.
As POGO once said, "We have met the enemy & they is us (you)."
After confirming this reality, please post results back here.
[Updated on: Fri, 06 June 2008 10:24] by Moderator Report message to a moderator |
|
|
|
| Re: PL/SQL Developer Debugging Hangs [message #325569 is a reply to message #325565] |
Fri, 06 June 2008 10:29 |
pmcginnis
Messages: 2
Registered: June 2008
|
Junior Member |
|
|
Thanks for your insight, but no, I can open up a PL/SQL Developer session completely new and run some procedure, with or without commits, and I still have the problem. I did notice also that if I turned off, in preferences, update watches after each step, and update call stack after each step, I get better results.
Hmmmm.
|
|
|
|
|
|
|
|
| Re: PL/SQL Developer Debugging Hangs [message #330186 is a reply to message #325557] |
Fri, 27 June 2008 16:16 |
coleing
Messages: 213
Registered: February 2008
|
Senior Member |
|
|
this is a well commented on problem with plsql developer, and you have obviously looked it up, as what you have done in the preferences is the suggested solution.
I get the problem periodically as well, and although I cant pinpoint it, it always seems to be packages which consume a lot of memory and use lots of arrays (which plsql developer debugger is rubbish with).
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
