On 10/10/2011 4:34 AM, Marcel wrote:
Working with Delphi 2005 and Eurekalog 188.8.131.52.
When I trap memory leaks in Eurekalog, my application runs fine.
If I don't trap memory leaks, the application crashes !
If I deactivate Eurekalog, it crashes too !
Amazing, no ?
Is there any explanation ?
Some types of uninitialized variable bugs can be masked by shifting your EXE memory footprint. If the uninitialized variable is filled with *reasonable* random junk, then your program works. If, due to changes in your program that move it around in memory and the same variable is now filled with *unreasonable* random junk, then your program behaves badly.
EL is simply pushing portions of your EXE higher in memory. If it wasn't EL, then something else that caused the same shift could do the same thing.
You need to find out where the program crashes and look backwards from there. The spot where it crashes is probably not where the problem is. You need to find our which variable is causing the problem and that can be anywhere.
Kevin G. McCoy