MSIR.0918 Debugging terminated, DEBUGPAG exceeded.: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
A Sirius/Janus Debugger session was terminated because the session required more than DEBUGPAG pages to hold Debugger work info. Since the bulk of required space for the Debugger is to hold the source lines of the procedures being compiled (after dummy string substitution), this suggests that the Debugger is being used against large procedures. DEBUGPAG should probably be increased (in the user0 system parameters), though it might be a good idea to also increase the size of CCATEMP before doing so, if there will be many concurrent debugger sessions. | A Sirius/Janus Debugger session was terminated because the session required more than DEBUGPAG pages to hold Debugger work info. Since the bulk of required space for the Debugger is to hold the source lines of the procedures being compiled (after dummy string substitution), this suggests that the Debugger is being used against large procedures. DEBUGPAG should probably be increased (in the user0 system parameters), though it might be a good idea to also increase the size of CCATEMP before doing so, if there will be many concurrent debugger sessions. | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0800 - MSIR.0999]] | ||
Revision as of 16:08, 13 August 2015
A Sirius/Janus Debugger session was terminated because the session required more than DEBUGPAG pages to hold Debugger work info. Since the bulk of required space for the Debugger is to hold the source lines of the procedures being compiled (after dummy string substitution), this suggests that the Debugger is being used against large procedures. DEBUGPAG should probably be increased (in the user0 system parameters), though it might be a good idea to also increase the size of CCATEMP before doing so, if there will be many concurrent debugger sessions.