[omniORB] question regarding ORB initialization in DLLs and somegeneral problems

[Andrew Buza]

On Mon, Jun 22, 2009 at 10:14 AM, William Bauder <bill at simplified.biz>wrote:

>
>
>  -----Original Message-----
> *From:* omniorb-list-bounces at omniorb-support.com [mailto:
> omniorb-list-bounces at omniorb-support.com] *On Behalf Of *Andrew Buza
> *Sent:* Friday, June 19, 2009 5:39 PM
> *To:* omniORB-list at omniorb-support.com
> *Subject:* [omniORB] question regarding ORB initialization in DLLs and
> somegeneral problems
>
>
>
> I'm using omniORB-4.1.3 (compiled with /Zc:wchar_t) and msvc 7.1.6030. The
> same projects are also built with msvc 8 and work fine. The application that
> loads my DLLs (Adobe InDesign) appears to be involved in (de)allocation in
> some way since one of its dlls appears in the call stack between the call to
> operator delete[] in my code and the implementation in ntdll.dll. Might this
> be the source of some of my problems?
>
> That sounds like someone snuck an operator[] delete or #defined free
> somewhere. Check the header(s) for the offending dll.
>
>
>
Peeking at the symbol table of the DLL shows that it does contain overloaded
new[] & delete[] operators. However, they aren't declared in the headers
anywhere that I can find.

In any case it seems the problems I'm having aren't anything specific with
omniORB so I'll take my questions to a more general audience.

Thanks for your help, everyone.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20090622/586d1858/attachment.htm