Hi Nathan, > Sorry for this second response, No problem. Extra chatter is better than no chatter.
> You seem to have forgotten the -D switch to nm(1). Thanks. I'll verify and close the bugs if necessary. : The first call to dlsym resulted in a crash. When examining : screen output and the full back trace, I noticed libcrypto++ : had two different addresses - one due to the link-loader, the : second due to dlopen. So it appears something is munged. Any ideas on why I would have two libcrypto++ in memory? I'm assuming two distinct addresses mean two separate copies. dlopen was called with RTLD_GLOBAL. In the Windows world, a second, third, ...., call to LoadLibrary returns the first mapping (and only bumps a reference count). Jeff On Thu, Oct 14, 2010 at 10:28 PM, Nathan Phillip Brink <[email protected]> wrote: > Sorry for this second response, I forgot to include the mailing list in the > first one as this mailing list doesn't munge Reply-To (or whatever that > header's called). > > On Thu, Oct 14, 2010 at 10:09:30PM -0400, Jeffrey Walton wrote: >> r...@bruno:/# nm /usr/lib/libcryptopp.so | grep g_nullNameValuePairs >> nm: /usr/lib/libcryptopp.so: no symbols >> r...@bruno:/# nm /usr/lib64/libcryptopp.a | grep g_nullNameValuePairs >> U _ZN8CryptoPP20g_nullNameValuePairsE >> 0000000000000010 B _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> U _ZN8CryptoPP20g_nullNameValuePairsE >> r...@bruno:/# nm /usr/lib64/libcryptopp.so | grep g_nullNameValuePairs >> nm: /usr/lib64/libcryptopp.so: no symbols > > You seem to have forgotten the -D switch to nm(1). Most shared objects only > have symbols of a type that nm will only print when the -D switch is used. > Likewise, unshared objects don't have any shared symbols. > > -- > binki > > Look out for missing apostrophes! > -- 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.
