Re: Adding Blank Line In Source Causes Change In Executable

Morris, John M CIV NSWCDD, Q34 <john.m.morris@navy.mil> wrote:


(snip)
> I am not intentionally including debug information in my builds.


Some compilers may generate debugging by default. Others may not
even have an option to turn it off. On many systems, a link-time
option is needed to put the compiler generated debugging data into
the executable, but maybe not all.


> I assumed that blank lines in the source would have no impact on
> the executable, but that appears to be incorrect.


A common debugging feature allows for the printing of statement
numbers in error messages, which means that they have to get into
the executable. The usual optional debugging information, for
example -g in GNU compilers, allows variable names to be included
for debugging. Variable names tend to take up a lot more room
than just statement numbers.


Including source statement numbers does not necessarily follow
the same debugging option, and may even not be optional.


-- glen

Return to the comp.compilers page.
Search the comp.compilers archives again.