Kbase 18182: Debugger Segment Exceeded - Error 3307
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/08/1998 |
|
Debugger Segment Exceeded - Error 3307
If you are getting error 3307 indicating that the debugger segment
has exceeded its maximum size you must take some of your code and
move it into other source files.
There is only one debugger segment per compiled source program and
once that segment is full the source code will not compile. We have
entered a bug report asking that when this situation happens during
the program compilation that the compilation should succeed but that
the resulting R-Code should be marked as non-debuggable instead of
generating a compilation error.
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
You may be interested in knowing what actually gets stored in the
debugger segment. The following list provides that information:
- 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.