Recommended practice wrt. EurekaLog activation

[Harry Bego]

Hi,

I'm always keen to use the release settings in the compiler options when
issuing a new software version. But when EurekaLog is activated, it includes
debug info in the executable. So I have two questions:

- What is recommended practice when using EurekaLog? Certainly not to keep
it always active. Use it for a brief period of time when issuing a new
release, with a few users? Or just when tracking down a problem?

- When compiling, shouldn't EurakaLog notify that it is switching on
debugging settings in your compiler preferences? As far as I can see, it is
not documented in the Help info that EurekaLog does this either.

Thanks for any comments,

Harry

[admin]

Hi,

Harry Bego wrote:
> Hi,
>
> I'm always keen to use the release settings in the compiler options when
> issuing a new software version. But when EurekaLog is activated, it includes
> debug info in the executable. So I have two questions:
>
> - What is recommended practice when using EurekaLog? Certainly not to keep
> it always active. Use it for a brief period of time when issuing a new
> release, with a few users? Or just when tracking down a problem?
>
> - When compiling, shouldn't EurakaLog notify that it is switching on
> debugging settings in your compiler preferences? As far as I can see, it is
> not documented in the Help info that EurekaLog does this either.
>
> Thanks for any comments,
>
> Harry

The problem really did not exists because the only debug information
that EurekaLog enables are information that are included in the final
DCUs, TDSs or OBJs files not in the final .EXE file.

So you can safely leave these settings enabled.

In fact you can check the final .EXE file size before and after activate
these debug information to see that it's always the same! :)

You can find this option in:
"Project/Options.../Compiler/Debugging/Debug Information".

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!