Stephan Bergmann wrote: > > Could it be that there are multiple instances of stdc++/gcc_s libraries > in the process (from both /opt/openoffice.org/ure/lib and from the > system)? That could explain that exception handling does not work > reliably (so an IOException that should be caught in a try-block would > erroneously escape it)---it would not explain the sleep(1) fix, though. > The easiest way to check this would be to temporarily move > /opt/openoffice.org/ure/lib/libgcc_s.so.1 and > /opt/openoffice.org/ure/lib/libstdc+++.so.6 out of the way. >
I did as you suggested above. My build process succeeded as usual but unfortunately the problem still exist. Stephan Bergmann wrote: > > Also, where do you place libooo.so? Is the executable calling into > libooo.so also built against the OOo SDK? How does it access libooo.so > (via dlopen, or is it directly linked against it)? Do you use any > LD_LIBRARY_PATH when calling the executable? What is the output of > calling ldd on the executable and on libooo.so, resp.? > No, the executable calling libooo.so is not build against the OOo SDK. My executable is using libooo.so via dlopen etc. And yes, I use LD_LIBRARY_PATH=/opt/openoffice.org/ure/lib/. regards petteri -- View this message in context: http://old.nabble.com/IOException-OOo-3.1.1-tp27226808p27335401.html Sent from the openoffice - api dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
