How to deploy with eurekalog?

1.8k views Asked by At

I'm having a problem trying to deploy an application with eurekalog to solve some memory leaks that happen in a specific scenario. When I configure my app project to use eurekalog under the delphi IDE and run through the IDE, it works perfectly, reporting leaks and exceptions. When I run the exe outside the IDE it doesnt report anything.

Is there a special configuration to deploy the application with eurekalog?

thanks

3

There are 3 answers

2
GabrielF On

The IDE won't report anything... there should be a window from EurekaLog provinding call stack and some other info. From EurekaLog official documentation:

Short answer:

  1. To solve problems with non-working, partial or misleading call stack - clear .map, .tds and .dcu files of your project and be sure to: ●(Delphi) enable "Compiler"/"Debug information", "Linker"/"Map file" = "Detailed". ●(C++ Builder) enable "C++ Compiler"/"Debugging"/"Debug information", "C++ Compiler"/"Debugging"/"Debug line number information", "C++ Linker"/"Full debug information", "C++ Linker"/"Output"/"Map file" = "Detailed segment map".

  2. To increase help level of EurekaLog: ●(Delphi) enable "Compiler"/"Stack frames", "Compiler"/"Range checking" and "Compiler"/"Use Debug DCUs" options and make "Project"/"Build all". ●(C++ Builder) disable "C++ Linker"/"Output"/"Map with mangled names" option, enable CodeGuard for you application (some options may conflict with EurekaLog).

If that doesn't help, you should provide more information: What happens when an exception is triggered by your application? Does an EurekaLog window appears?

0
IceCold On

EurekaLog is overkill for what you want (it will also increase the compilation time 3-5 times). If all you want is to detect a memory leak, use FastMM4. It is already delivered with Delphi and is cheaper that EurekaLog (cheap=free :) ).

How to enable full debug mode in FastMM4?

PS: if you really MUST use EurekaLog, use v6. v7 is totally unstable.

0
Alex On

You forgot to turn off "Active only when running under debugger" option, which is enabled by default.