🚀 go-pugleaf

"Eyyub Volkan �ektimur" <evcektimur@prokon.com.tr> wrote:

>so, heap is not a memory block that is given to users, it's a kind of 
>management tool i guess. so, can we say that memory manager uses heap 
>structure to give memory chunks from bigger memory allocations and also 
>manages free operations etc... Can we say that, heap is a structure to hold 
>given allocations,frees,etc... to share bigger allocation chunks taken by 
>GlobalAlloc ?

Close enough.

(Windows will have its own heap managers too - at the top end, there's
just raw memory, that GlobalAlloc will take chunks from.)

>i guess i need to check memory managers of EXE & DLLs not heaps. If all of 
>them using the same memory manager, then there will be no heap corruption 
>problem. 

The RTL provides an exported memory manager, that provides the
new/malloc/... functions from a DLL rather than from within a LIB
whereby each linked executable gets its own copy. 

>         Is there any way in borland to check that loaded DLLs and EXE are 
>using the same memory manager ? in borland is the memory manager named as 
>RTL ? or is RTL mapped to microsoft's CRT ? does borland compiler have a 
>seperate memory manager tool (that is implemented in RTL) ? 

As far as I know, you have to manually check the link options, though
it's probably also possible to use the Dependency Walker tool to see if
all the items use the RTL. I'm not sure the name of that DLL, since the
only bit of my code that does this sort of thing happens to use my own
implementation of the same idea (dating back to 1991)(Yeah, my original
version allowed memory shared between processes - that went west when I
went 32-bit.).

(http://http://www.dependencywalker.com/ for the Dependency Walker
tool.)

Alan Bellingham
-- 
Team Browns
ACCU Conference 2008: 2-5 April 2008 - Oxford, UK