[omniORB] Problems with SGI and OmniORB-4.0.0

[Grobarcik Peter]

Hi all,

I did not look too deeply into the snippets send, but we got a simmilair
problem, because
the linker wrongly removed the "unreferenced" static initialisers, so there
was no codeset present.
It was not on SGI but on BS2000, but as far I know Siemens bought originally
the C/C++ stuff from SGI, so there is a chance. We just included an codeset
directly into the executable to test it. We do not have a final workaround
yet.

By all,

Peter

-----Ursprüngliche Nachricht-----
Von: Duncan Grisby [mailto:duncan@grisby.org]
Gesendet: Mittwoch, 15. Januar 2003 14:57
An: Mark Underwood
Cc: omniorb-list@omniorb-support.com
Betreff: Re: [omniORB] Problems with SGI and OmniORB-4.0.0 


On Tuesday 7 January, Mark Underwood wrote:

> The only change I had to make was to define OMNI_REQUIRES_FQ_CTOR after 
> the configure completed (this already seems to be fixed in cvs 
> development version).

Yes, that is already fixed in CVS.

> However, both the 4.0.0 and development versions dump core (SIGSEGV) 
> when calling CORBA::ORB_init.

[...]
> orbParameters::nativeCharCodeSet and orbParameters::nativeWCharCodeSet 
> end up as NULL which causes problems either with setting the 
> anyCharCodeSet/anyWCharCodeSet or in initialise_my_code_set().

That looks like the static initialisers for the code sets are not
running. I don't know why not. Try putting some debugging output in
the static initialisers (in cs-8859-1.cc for example), to see whether
they are running or not.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --
_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list