https://community.hpe.com/t5/operating-system-hp-ux/issues-with-shared-libraries-and-static-memebers/m-p/2886536#M719508 I had a similar problem. I traced it back to the following cause: When loading a shared lib written in C++ dynamically from a C program, the global static members do not get initialized. The remedies I found are: Either compile the C program with the C++ compiler, call the initilization code explicitly, or not to use global static variables in your library (if you own the code). <BR /><BR />You are probably referring to one of these remedies? <BR /><BR />I don't think there is a OS or compiler patch for this. However maybe there is one available in the meantime. Thu, 23 Jan 2003 11:27:35 GMT Martin Schneider_2 2003-01-23T11:27:35Z https://community.hpe.com/t5/operating-system-hp-ux/issues-with-shared-libraries-and-static-memebers/m-p/2886535#M719507 Hi,<BR /><BR />I have an issue with loading librarys on HPUX 11.00 and 11i, with gcc 3.2 using C++<BR /><BR />I had an problem with the dlopen call not correctly setting up the static classes correctly. Therefore I tried<BR /><BR />Load the Library<BR />Get the address of _GLOBAL__DI<BR />run that function<BR /><BR />This does work however I have a problem with shutdown causing a seg 11 fault. The only information I can find on this issue is around 3 years old. Please could someone confirm/deny if this approach is still required or has been fixed in this version of hpux and my makefiles are incorrect<BR /> Tue, 21 Jan 2003 12:24:01 GMT https://community.hpe.com/t5/operating-system-hp-ux/issues-with-shared-libraries-and-static-memebers/m-p/2886535#M719507 Stephen Hoare 2003-01-21T12:24:01Z https://community.hpe.com/t5/operating-system-hp-ux/issues-with-shared-libraries-and-static-memebers/m-p/2886536#M719508 I had a similar problem. I traced it back to the following cause: When loading a shared lib written in C++ dynamically from a C program, the global static members do not get initialized. The remedies I found are: Either compile the C program with the C++ compiler, call the initilization code explicitly, or not to use global static variables in your library (if you own the code). <BR /><BR />You are probably referring to one of these remedies? <BR /><BR />I don't think there is a OS or compiler patch for this. However maybe there is one available in the meantime. Thu, 23 Jan 2003 11:27:35 GMT https://community.hpe.com/t5/operating-system-hp-ux/issues-with-shared-libraries-and-static-memebers/m-p/2886536#M719508 Martin Schneider_2 2003-01-23T11:27:35Z