Tracy Pierce wrote:
>
> Hopefully, this tells the whole story...
>  ID DIVISION.
>  PROGRAM-ID. DBUGDEMO.
>  ENVIRONMENT DIVISION.
>  CONFIGURATION SECTION.
>  SOURCE-COMPUTER. HP3000 WITH DEBUGGING MODE.
>  SPECIAL-NAMES.
>      SW15 IS PARM1, ON STATUS IS DEBUG-ACTIVE;
>      .
>  PROCEDURE DIVISION.
>  DECLARATIVES.
>  GENERAL-DEBUGGING SECTION.
>      USE FOR DEBUGGING ON ALL PROCEDURES.
>  REQD-SILLY-PARAG-NAME.
>      DISPLAY DEBUG-LINE " " DEBUG-NAME " " DEBUG-CONTENTS
>      .
>  END DECLARATIVES.

The "with debugging mode" will generate a larger executable.  If you
don't set "with debugging mode" the "D" lines are treated as comments
and the resulting object file should be the same size.  The difference
is if you have "with debugging mode" the code has to be included to
accomodate the declarative hooks (a conditional test at each paragraph
marker), the constants to display the DEBUG-variables, and the
conditional code for the "D" lines.

The size penalty is worse with SYMBOLIC debug (Toolset or XDB) as well
as the code overhead, as this includes statement number markers in the
code.  But you get much more meaningful stack traces with SYMDEBUG than
without; especially if you optimize.  Fully optimized code gives you
very little useful info in a stack trace/:SETDUMP capture.

Jeff Kell <[log in to unmask]>