🚀 go-pugleaf

thanks for your answer. i don't think that borlndMM.dll is the one i'm 
searching for, because, when i try to set my memory managment 
(SetMemoryManager(...)) it does not handle C type malloc & free and also it 
does not handle new, new[], delete, delete[] on regular types... i guess 
it's used only in VCL, when i tried to create a VCL object, memory manager 
functions are triggered, but nothing else. thanks anyway,...

"dhoke" <dhoke.nojunk@east-shore.com> wrote in message 
news:4743226d$1@newsgroups.borland.com...
>
> "Eyyub Volkan �ektimur" <evcektimur@prokon.com.tr> wrote in message 
> news:4742dbe3@newsgroups.borland.com...
>> one more question;
>>
>> i traversed all modules loaded by EXE (EnumProcessModules) and queried 
>> that which module including "malloc" 
>> (GetProcAddress(modules[cx],"malloc")!=NULL). the result is ;
>>
>> malloc in C:\WINDOWS\system32\msvcrt.dll
>>
>> i was expecting to find "C:\WINDOWS\system32\CC3260MT.DLL" (i'm using bcb 
>> 6.0)
>>
>> does not borland have a seperate memory manager that handles malloc ? if 
>> there is, why malloc is in msvcrt.dll ? as i know CC3260* is the 
>> VCL-Compliant of CRT, so it's making more sense to include malloc in 
>> CC3260*.dll. does borland using microsoft's memory management DLL 
>> (msvcrt.dll) ? (if it's, CC3260* should be a mapper to msvcrt.dll) ... 
>> thanks again
>>
>
> At least for bds2006 (don't know about BCB6), and appears to for the 
> CB2007trial and radstudio2007trial versions:
>
> Borland(/CodeGear) does have its own memory management.  (Not sure what 
> you've found with your search.)
>
> Borland has a plug-in memory management architecture, whereby you can 
> (well some people can) replace the memory manager functionality.
>
> A replacement memory manager (borlndmm.dll), is part of product 
> installation, installed in the ...\bin directory of the installation tree.
>
> Borland's memory manager (since at least bds2006) is apparently a copy or 
> derivative of the FastMM memory manager 
> (http://sourceforge.net/projects/fastmm/).
>
> Borland's libraries are implemented such that a plugin replacement memory 
> manager will _not_ be used if an application/dll is linked with static 
> libraries (at least with bds2006.)
>
> You might want to redirect this topic to the .rtl newsgroup, wrt/ B/CG's 
> runtime library implementation.
>