[omniORB] OmniORB 304, windows debug DLLs

[Mann, Gary (London)]

Some Windows libraries (e.g. WinSock's WS2_32.dll) link with the release
version of MSVCRT.DLL. This gives the impression that you are linking with
both versions, as the debug version of omniORB links with release
WS2_32.dll, for which there is no debug build equivalent (it's part of the
OS).

This is by design, and causes no problems unless you try to use the operator
delete() in the debug version of MSVCRT to free memory allocated by operator
new() in the release version (or vice-versa). This shouldn't happen under
normal WinSock usage.

Gary

-----Original Message-----
From: Patrick Hubert [mailto:hubert@discreet.com] 
Sent: 19 April 2002 15:20
To: omniorb-list@uk.research.att.com
Subject: [omniORB] OmniORB 304, windows debug DLLs




Hello all,

Looking at the debug DLLs on windows (both those I've build and those
provided by omniORB_304_x86_win32.zip) I see that they link with both
MSVCRT.DLL and MSVCRTD.DLL... (I've used MicroSoft's Dependency Walker that
comes with MSVC 6.0)

Should it be this way?

>From what I remember reading from the omniorb mailing list, mixing both
debug and non-debug dlls usually brings problems...


I need to build debug OmniORB dlls that do not link with MSVCRTD.DLL.


Thanks

 -Patrick

--
Patrick Hubert
Work: +1.514.954.7233
Fax : +1.514.393.0110