Kbase P19038: Error (3307) : Debugger Segment Exceeded - running code in development mode.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/11/2004 |
|
Status: Verified
SYMPTOM(s):
<segment-name> has exceeded its limit of <segment-size> bytes, in <file-name> at line # <line-number>. (3307)
Debugger segment has exceeded its limit of <segment-size> bytes, in <file-name> at line # <line-number>. (3307)
CAUSE:
There is only one debugger segment per compiled source program and once that segment is full the source code will not compile
FIX:
Take some code and move it into other source files.
The following two things are major causes of "blowing" the debugger segment and it may be possible to eliminate the error by removing and/or moving these things to separate .p files:
- Temp-Tables
- Internal Procedures
The following list provides information about what actually gets stored in the debugger segment:
- Variable names and data types
- Buffer names
- Temp-Table descriptions
- Internal procedure information
- Trigger information
- User defined function information
- Executable line numbers
- Sources that comprise the .r file
The only thing needed in order to debug R-Code that is not placed in the debugger segment are the line numbers stored with each executable statement in the action cell segment(s) identifying what line the statement is on.