When i debug a script, Plyxon breaks execution very many times.
The result is that i have to click "Run to completion" maybe 50 times for some scripts.

My theory is that maybe it breaks execution as soon as a new package/method is invoked?

The database packages i debug are rather big and advanced

Can you provide an example?

I tried to create some test-packages to see if my theory held up. It didnt.
So i figured out what it was breaking on in my production code instead and managed to replicate that.

In this example the debugger breaks when a cursor calls a function.
I attached the example package and test-script.

1. Create the package and add debug information.
2. Open the test-script and click "Debug current command (F9)" button.
3. Click "Run to completion" button.
4. Notice that the bugger stops on line 32 (see example screenshot)

ps. not sure why, but when i created the package and tried to debug it in the same instance of Plyxon, it failed to hit breakpoints no matter how i tried.
After restarting Plyxon breakpoints started to be hit. Not sure if this affects the attached example; but if you can't recreate the issue try restarting Plyxon

ps2. My oracle version:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.22.0.0.0

Thanks, we'll investigate!