[omniORB] compiling omniORB3 on NT -- Assertion failure

[Lars Immisch]

<fontfamily><param>Helvetica</param>> I am not sure if, in Windows
debugging mode, a dll does not treat the
<nofill>
> executing process' heap as if it were its own -- the terms "local heap of a
> DLL" maybe just semantics for MSVC debugger's accounting system for keeping
> track of memory allocated/deallocated from "the global heap" using the dll's
> exported functions.
> 
> A MSVC++ expert (which I am not) would probably know
> whether this is true.
</nofill>

Not that I am an expert, but as far as I remember, a Win32 DLL has it's
own heap if it's linked against the static C runtime libraries, but will
share the heap with the process if both use the DLL C runtime libraries.
If it is required that a process frees memory allocated by the omniORB
DLLs, I would recommend you check that both the omniORB libraries and your
process are linked against the dynamic libraries.


Hope this helps,


Lars Immisch

--

lars@ibp.de

</fontfamily>