Program too large and config of Never Add Debug Info

[joel]

Hello,

I understand the message "Program too large" when compling is a database issue, and not a PL/SQL Developer issue.

However, I have the "large" package excluded from adding debug info in Preferences - Debugger, in the "Never add debug info for objects" section. This works well, except when I do a Tools-Compile Invalid Objects. It seems that the debug info is still sent when compling my excluded package, so I have to recompile that individual package when the rest of the list is compiled.

Not a showstopper, but hopefully something to fix for the next release.

Thanks,
Joel Cumming

 

[Marco Kalter]

Seems like a bug. We'll check it out for the next release.

 

[Stew Stryker]

Originally posted by joel:
[QBPreferences - Debugger, in the "Never add debug info for objects" section.[/QB]

Speaking of this preference...

Might it make sense for the default value of this to be off? It seems that every new user has trouble compiling their code at first, until someone here tells them to turn this off.

Just my $.02.

 

[joel]

I am still after my DBA... it only gives us problems on one DB, the other 7 are fine. It would be nice to track down the parameter that is reponsible for the error and increase the allowable size.... that seems like the ultimate solution.