Delphi compiler options for Debugging

Question

What effect do the options in the image below have on the finally binary?

I first compiled my application with them enabled and the compiled binary file size was 7,606,272 bytes. Then I manually switched them off...and the size was unchanged. I also used these compiler switches (included in every file using a .inc file) to do the same thing:

    {$D-}       // Remove "Debug information"
    {$L-}       // Remove "Local symbols"
    {$Y-}       // Remove "Reference info/Definitions only"
    {$C-}       // Remove "Assertions"

Same file size. The help does say that debugging information goes into the DCU (object) files and I've confirmed this is correct (they're smaller with the options off). Compilation and linking time is so fast, though, its hard to tell if there is a difference time-wise.

Does toggling these options have any effect on the final binary (eg. performance enhancement)? It doesn't appear to affect the size of the binary, in any case.

Are you sure that this information is not present in the help? — LU RD
– LU RD, Commented Jul 24, 2015 at 14:51
@LURD: The help does say that debug information goes into the DCU (object) files (I'll add that to the question, thanks). I have confirmed that the DCU files are indeed smaller with debug information compiled out. Compilation and linking is so quick that I can't see any time difference. The help is silent about what effect (if any) these options have on the final binary, hence the question. — AlainD
– AlainD, Commented Jul 24, 2015 at 14:58
In modern delphi help, it says that it does not affect the final exe file size. — LU RD
– LU RD, Commented Jul 24, 2015 at 15:00
@LURD: Aah, thanks. Does that mean there is zero benefit to switching these options off for RELEASE code? — AlainD
– AlainD, Commented Jul 24, 2015 at 15:03
Just a link to help, docwiki.embarcadero.com/RADStudio/en/… — LU RD
– LU RD, Commented Jul 24, 2015 at 15:04

David Heffernan · Accepted Answer · 2015-07-24 15:02:52Z

3

The top three options have no effect on the binary. They only impact on whether or not debugging information is produced in the dcu files.

The assertions option determines whether or not Assert statements are included or not. That affects the executable.

Debug DCUs determines whether or not the RTL/VCL dcu files contain debug information. Also, the debug versions of these dcu files are built unoptimized to make debugging better. So that also affects the code that goes in the executable.

answered Jul 24, 2015 at 15:02

David Heffernan

616k46 gold badges1.1k silver badges1.5k bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

AlainD Over a year ago

Ok, thanks. The in-built help with Delphi-7 was missing the critical bit "does not affect the size or speed of the executable program", see the comment from LU RD.

David Heffernan Over a year ago

My release build includes debug info so that I can get good post mortem debugging info.

AlainD Over a year ago

Good point. Including the debug information also allows one to set breakpoints and step through any {$IFDEF NDEBUG} code, though I have very little code specific to NDEBUG and anyway do most debugging in DEBUG code. If the NDEBUG application were to crash (away from the development machine), does having the debug information help?

Collectives™ on Stack Overflow

Delphi compiler options for Debugging

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related