Hi all, valgrind is reporting me this, not sure if it is a false positive: ==8580== 32 bytes in 1 blocks are still reachable in loss record 5 of 10 ==8580== at 0x4C275D8: malloc (vg_replace_malloc.c:236) ==8580== by 0x13787F21: CRYPTO_malloc (in /lib/libcrypto.so.0.9.8) ==8580== by 0x137E747C: sk_new (in /lib/libcrypto.so.0.9.8) ==8580== by 0x13504399: ??? (in /lib/libssl.so.0.9.8) ==8580== by 0x135045A8: SSL_COMP_get_compression_methods (in /lib/libssl.so.0.9.8) ==8580== by 0x1350AA0F: SSL_library_init (in /lib/libssl.so.0.9.8) ==8580== by 0x8C78864: boost::asio::ssl::detail::openssl_init<true>::do_init::do_init() (openssl_init.hpp:51) ==8580== by 0x8C95848: boost::asio::ssl::detail::openssl_init<true>::do_init::instance() (openssl_init.hpp:85) ==8580== by 0x8CC1911: global constructors keyed to WtReply.C (openssl_init.hpp:124) ==8580== by 0x8CC2825: ??? (in /usr/local/lib/libwthttp.so.3.1.6) ==8580== by 0x8C5A99A: ??? (in /usr/local/lib/libwthttp.so.3.1.6) ==8580== by 0x7FF00085F: ???
it seems that somehow an instance of openssl_init::do_init is not destroyed, that's strange because the openssl_init::do_init is a singlethon with the instance() method returning a boost::shared_ptr. So the only way is someone allocating on the heap a class carrying somehow a boost::shared_ptr<openssl_init::do_init>. Regards Gaetano Mendola -- cpp-today.blogspot.com ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
