We experience errors when trying to use cryptopp as shared lib from more than one other shared libs. the scenarios are as follows (all libraries are shared libs):
scenario 1: working library X --uses--> cryptopp libraries A, B, C --use--> X Apache --loads--> A, B, C this works fine. scenario 2: not working library X --uses--> cryptopp libraries A, B --use--> X library C --uses--> cryptopp (directly!) also C --uses--> X Apache --loads--> A, B, C We get an error (crash) on something with name-value pairs. My hunch is that, even though the OS should load a shared lib only once, some initialization occurs twice and fails on some static or global update. Is there some implicit initialization of cryptopp that shouls happen only once? are there some statics/globals used? Has anybody experienced this? I'd be grateful for any tips on this problem. my environment: cryptopp: 5.5.2 (installed it with package manager, which brought only the shared lib version) OS: Linux bagvapp 2.6.18-164.2.1.el5.plus #1 SMP Fri Oct 9 12:34:43 EDT 2009 i686 i686 i386 GNU/Linux (centOS package under VM) GCC: gcc -v output: Using built-in specs. Target: i386-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man -- infodir=/usr/share/info --enable-shared --enable-threads=posix -- enable-checking=release --with-system-zlib --enable-__cxa_atexit -- disable-libunwind-exceptions --enable-libgcj-multifile --enable- languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk -- disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.4.2- gcj-1.4.2.0/jre --with-cpu=generic --host=i386-redhat-linux Thread model: posix gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) thanks a lot! david -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
