[omniORB] Threading problems

[bjornw@fairplay.no]

Michael Sommerville <msommer@ptc.com> writes:

> Hi,
>=20
> I've been trying to use omniORB together with one of our
> products which has a 'C' API to an Oracle based
> application. =20
>=20
> I'm not at all sure why its happening, but omniORB is=20
> crashing on initialisation in the thread libray.  Presumably
> there is some conflict between the threading used in the=20
> omnithreads library and that used within the API.  I tried=20
> recompiling to use Solaris instead of Posix threads with no
> success. =20
>=20
> Here's what I get from dbx.
>=20
> (process id 17840)
> signal SEGV (no mapping at the fault address) in thr_self at
> 0xee2db2f8
> thr_self+0x4:   ld      [%g7 + 0x24], %o0
> (dbx) where
> =3D>[1] thr_self(0x23fbe8, 0x0, 0x1, 0x23fbe8, 0x0, 0x64), at
> 0xee2db2f8
>  [2] omni_thread::init_t::init_t(0x1, 0xee252e9c, 0x23fbe8,
> 0x23fba0, 0x0, 0xee043288), at
>  [3] __STATIC_CONSTRUCTOR(0xee075ec4, 0xee2b6b60, 0x20e,

I do not have a solution to your problems, but you might want to
check and verify that your thred-library works correctly.
Try making a small threaded program and be sure you use the same
compiler as you use for compiling omniORB. Maybe some compiler-
options like '-threads' are missing? Or that the omniORB libraries
were not linked correctly with '-shared/pic' flag (or whatever your=20
compiler accepts as flags for creating shared libs.)

bjornw>
--=20
-------------------------------------------------------
Bj=F8rn Wennberg              email: bjornw@fairplay.no=20
                               ms: +47 950 82 657
Senior Programmer           phone: +47 22405538
FairPlay International AS     fax: +47 22405539