Hi,
I first time noticed it when I tried make a release
build shortly after downloading BDS2007R2 April
hotfix, so at the beginning that was what I blamed.
However, a few days earlier I also downloaded Indy April
snaphsot. It would work fine in my non-release builds...
However, I get a call stack error when:
{$undef EnableMemoryLeakReporting} in FastMM
I have traced it to Indy:
System.InitUnits;
{$IFDEF MSWINDOWS}
TProc(P)();
{$ENDIF}
IdStack.Initialization
{$IFDEF REGISTER_EXPECTED_MEMORY_LEAK}
IndyRegisterExpectedMemoryLeak(GStackCriticalSection);
{$ENDIF}
IdGlobal
{$IFDEF VCL10ORABOVE}
Result := System.RegisterExpectedMemoryLeak(AAddress);
{$ELSE}
*System.RegisterExpectedMemoryLeak* then calls itself recursively...
The reason is that since my FastMM options have not overriden
*MemoryManager.RegisterExpectedMemoryLeak* the
System.RegisterExpectedMemoryLeak calls itself again and again...
Just figured I would post my findings.
best regards
Thomas Schulz
