Thread View: borland.public.delphi.language.basm
4 messages
4 total messages
Started by dk_sz
Sun, 20 Apr 2008 23:54
Just installed Delphi 2007 April 08 patch...
Author: dk_sz
Date: Sun, 20 Apr 2008 23:54
Date: Sun, 20 Apr 2008 23:54
54 lines
2077 bytes
2077 bytes
Hi,
I got the new update from:
http://cc.codegear.com/item/25495
Bad idea!
Seems like it breaks some of my FastMM 4.78 builds.
I get EStackOverflow with message "Stack overflow"
With callstack leading up to exception being a long (...) series of calls
RegisterExpectedMemoryLeak(nil)
RegisterExpectedMemoryLeak(*address*)
RegisterExpectedMemoryLeak(*address*)
RegisterExpectedMemoryLeak(*address*)
RegisterExpectedMemoryLeak(*address*)
... and so on ...
My FastMM options are these:
{$I FastMM4Options.cur.inc}
{$UNDEF ForceMMX}
{$UNDEF ASMVersion}
{$UNDEF FullDebugMode}
{$UNDEF RawStackTraces}
{$UNDEF CheckHeapForCorruption}
{$UNDEF EnableMemoryLeakReporting}
{$UNDEF UseOutputDebugString}
{$UNDEF DetectMMOperationsAfterUninstall}
{$UNDEF Align16Bytes}
{$UNDEF UseCustomVariableSizeMoveRoutines}
{$DEFINE AssumeMultiThreaded}
{$DEFINE ASMVersion}
-- Does not happen if I add --
{$DEFINE FullDebugMode}
{$DEFINE RawStackTraces}
{$DEFINE CheckHeapForCorruption}
{$DEFINE EnableMemoryLeakReporting}
{$DEFINE ClearLogFileOnStartup}
{$DEFINE UseOutputDebugString}
Any ideas on how to solve?
(except slapping myself to unconsciousness)
bestr egards
Thomas Schulz
Re: Just installed Delphi 2007 April 08 patch...
Author: dk_sz
Date: Mon, 21 Apr 2008 10:18
Date: Mon, 21 Apr 2008 10:18
22 lines
1284 bytes
1284 bytes
> With callstack leading up to exception being a long (...) series of calls
Callstack is
(until stack exception)
RegisterExpectedMemoryLeak(*address*)
RegisterExpectedMemoryLeak(*address*)
RegisterExpectedMemoryLeak(*address*)
...InitUnits;
System@StartExe
System@InitExe
if I have
{$DEFINE EnableMemoryLeakReporting}
the stack exception does not happen... Quite odd...
best regards
Thomas Schulz
Re: Just installed Delphi 2007 April 08 patch...
Author: dk_sz
Date: Mon, 21 Apr 2008 10:48
Date: Mon, 21 Apr 2008 10:48
13 lines
1296 bytes
1296 bytes
> if I have
> {$DEFINE EnableMemoryLeakReporting}
> the stack exception does not happen... Quite odd...
It think it is odd this error happens only
happens when this defne is *undef*... And yet
System@RegisterExpectedMemoryLeak gets called?
Can this be related to if they have fixed a memory leak
in Delphi 2007 April hotfix (changelog says OpenXML)
best regards
Thomas Schulz
Re: Just installed Delphi 2007 April 08 patch...
Author: dk_sz
Date: Mon, 21 Apr 2008 13:34
Date: Mon, 21 Apr 2008 13:34
44 lines
2065 bytes
2065 bytes
>> {$DEFINE EnableMemoryLeakReporting}
>> the stack exception does not happen... Quite odd...
I would like to correct myself...
I am not sure April patch is alone / at-all to blame.
I tracked the problem down to Indy snapshot (few days old)
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 call
calls itself again and again and again...
I am still wondering if perhaps April patch has
messed with some default define or...?
This is simply first time I have tried making a release build
without *EnableMemoryLeakReporting* since updating Indy.
Anyways, this is probably the wrong group! Sorry!
best regards
Thomas Schulz
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads