Ian Lance Taylor-3 wrote: > > Please don't post a core dump, as there is nothing we could do with > that. > > A crash in a mutex call does not necessarily mean that libgcc_s.so is > at fault. It suggests that something has gone wrong while running > global constructors. > > Ian > ok, the global constructors in the 3rd party library seem to work fine when you create an executable. it's only when you create a ".so" shared object link against the 3rd party library and then use dlopen() to load the module that this problem occurs. when i link to create executable, libgcc_s is not referenced. when i link to form a shared object, libgcc_s is referenced (by ldd). maybe it's not libgcc_s, i certainly can't prove it. if not, then i am stuck. why else might a 3rd part library work when in executable form, but crash on dlopen when in shared object form? -- View this message in context: http://www.nabble.com/libgcc_s-dependency-when-linking-with--shared-tf2781647.html#a7765701 Sent from the gcc - Help mailing list archive at Nabble.com.
