[omniORB] MFC+omniORB3004 rootContext->resolve(name) crash

[Alexios Ballas]

The problem is solved...

I had to remove _WINSTATIC from the macros...

thanks a lot for your help

Alexis


At 12:45 11/02/02 +0000, Duncan Grisby wrote:
>On Tuesday 29 January, Alexios Ballas wrote:
>
> > LINK : warning LNK4089: all references to "omniDynamic304_rt.dll" 
> discarded
> > by /OPT:REF
> >
> > Which I don't think that makes any difference to my problem as I also get
> > it when I link my Win32 console application that runs properly.
>
>That's probably OK.
>
> > I tried to set TraceLevel like this:  omniORB::TraceLevel = 10;
> > but I got an "unknown exception" again, I don't know why...maybe I 've put
> > it in the wrong place.
>
>If that fails, it's a good sign that things are confused about linking
>formats. Windows is very mysterious in this regard. Try tweaking the
>various debug settings to see if that helps.
>
>[...]
> > I am using "Multithreaded DLL".Debug and release libs seams to be fine:
> > Release:omniORB304_rt.lib omniDynamic304_rt.lib omnithread2_rt.lib
> > wsock32.lib advapi32.lib
> > Debug:omniORB304_rtd.lib omniDynamic304_rtd.lib omnithread2_rtd.lib
> > wsock32.lib advapi32.lib
>
>Those sound right, but there are a few debugging settings that can
>affect things. Try changing anything to do with memory allocation
>debugging.
>
>Sorry I can't be more specific.
>
>Cheers,
>
>Duncan.
>
>--
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --