Using the PL/SQL Developer "Test Window", I'm used to debugging and have been doing it for years. When an exception is raised, the tool normally provides me with a popup-message to report the error, and ti gives me an option to open the stack-trace screen, which is great.

However, the behaviour seems to have inexplicably changed over the past few days. It feels to me like it's a PL/SQL Dev config issue, but I'm not aware of having changed anything, and I haven't found any configs that would seem to control this anyway.

As a demonstration, see the attached 2 screen-shots. When I explicitly raise an exception in the Test Window, I get a popup-box:

`BEGIN
Raise_Application_Error(-20110, 'Something bad happened');
END;`

However, if I wrap that exception inside a PL/SQL package and call the top-level package, I no longer get a popup-box. Instead, the error message is relegated to the status-bar, and I get no option to open the stack trace.

What's happened? Is this something I changed? I'm pretty sure the Oracle DB hasn't changed any debug settings, because I can replicate the problem on multiple databases for multiple clients.

`BEGIN
Error_SYS.Record_General ('AuxInfo', 'ERR: Something bad happened!');
END;`

Check the DSA dialogs in the preferences. Remove the entry >ViewStackDump<.
Hope this helps.

I'm feeling a bit stupid here, but what are the DSA dialogs? I can't find any reference to "View Stack Dump" in the PL/SQL Developer Preferences dialog-box.

Configure -> Preferences -> Options (under User Interface in left pane) -> "DSA Dialogs..." button at bottom on right.

Good call!
How did I get through 20 years of using this tool without knowing this functionality!
Thank you!