[omniORB] Problems with OmniORB 3 on AIX
Michael J. Donahue
mdonahue@McLeodUSA.com
Thu, 3 Aug 2000 18:52:55 -0500
Sven -
Your problem could be related to the pthread version that the .mk file you are
using
implements. This was an important change when moving from AIX 4.2 to 4.3. If
you
change the -DPthreadDraftVersion value on or about line 134 from "8" to "10" and
rebuild ALL object files, libraries, and executables you fix your problem.
Either
way you should update this version anyway.
Hope it helps,
- Mike
Sven Eklund <sek@leissner.se> on 08/03/2000 05:04:20 PM
To: "'omniorb-list@uk.research.att.com'" <omniorb-list@uk.research.att.com>
cc: (bcc: Michael J. Donahue/MCLEOD)
Subject: [omniORB] Problems with OmniORB 3 on AIX
Hi!
I have problems to get omniORB 3.0 running on AIX 4.3.1 with xlC-compiler
3.1.4. I am using the script powerpc_aix_4.2.mk .
Everything is compiling. The problem is a coredump at the first line of
CORBA::ORB_init(...):
omni_tracedmutex_lock sync(orb_lock);
It happens in every program that calls this function (omniNames for
example).
I think it may have to do with initialization of the static member orb_lock
(static omni_tracedmutex orb_lock;). Maybe problems with shared library?
The constructor does not seem to be called at all. I have also tested to
compile omniOrb 2.5.0 on the same computer and it works fine. 2.5.0 has also
the same type of static declaration and uses shared libraries. I use the
same parameters for makeC++SharedLib_r in both versions.
Does anyone have any suggestions what can be wrong? Maybe parameters or
definitions that can cause this in 3.0?
Appreciate every suggestion.
Thanks in advance.
Sven Eklund
Leissner Data AB
Sweden