Can the debug file be broken off of the main exe ?

[JimHanson]

Hello!

Can the debug data be broken off of the main EXE and then perhaps compressed somehow (so our entire debug stack is not getting distributed to the world) ?

(like the borland tdsstrip.exe utility....)

Thanks!

[admin]

Hi,

JimHanson wrote:
> Hello!
>
> Can the debug data be broken off of the main EXE and then perhaps
> compressed somehow (so our entire debug stack is not getting
> distributed to the world) ?
>
> (like the borland tdsstrip.exe utility....)
>
> Thanks!

Yes, it theoretically possible, but this stop any EurekaLog functionality.

So why simply not disable EurekaLog if you did not want its debug
information? :)

--
Best regards...

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

[JimHanson]

Hi Fabio,

Sorry, let me explain this a different way.

a) We can of course compile with debug info. But in many cases the exe is MUCH larger.

b) Also, now all our debug info is now public, which makes it a little too easy to reverse engineer our code

So what I am asking for here is:

1) Reduced debug info footprint (e.g. compressed in some way). I think the Eurekalog compiler may already do this.

2) For the debug info to be encrypted or obfuscated in some way, so that it is not all in clear. (This could be either with the debug info attached to the exe or as a separate file.)


Thank you!

[admin]

Hi,

JimHanson wrote:
> Hi Fabio,
>
> Sorry, let me explain this a different way.
>
> a) We can of course compile with debug info. But in many cases the exe
> is MUCH larger.

But usually the EurekaLog debug info have a size of about 0.5% - 4% of
the final .exe file.

Verify to have unchecked the "Project\Compiled\Use Debug DCUs" the
"Project/Linker/Include TD32 debug info" and the "Project/Linker/Include
remote debug symbols" options.

> b) Also, now all our debug info is now public, which makes it a little
> too easy to reverse engineer our code
>
> So what I am asking for here is:
>
> 1) Reduced debug info footprint (e.g. compressed in some way). I think
> the Eurekalog compiler may already do this.

EurekaLog just do this.

> 2) For the debug info to be encrypted or obfuscated in some way, so
> that it is not all in clear. (This could be either with the debug info
> attached to the exe or as a separate file.)

EurekaLog just do this using a customizable password (as default is empty).
You can set the password via "Project/EurekaLog
Options.../Advanced/Call-Stack Options/Encryption Password).

I hope to have answered to your question, otherwise don't hesitate to
recontact to me, ok? :)

> Thank you!

--
Best regards...

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

[JimHanson]

Thank you!

This is all great and perfect!

We will take it from here.