[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37699 ] Albert Strasheim commented on AMQCPP-27: ----------------------------------------
Seems like there's still a mior issue with the threads on Linux. Valgrind says: ==10818== 8,640 bytes in 60 blocks are possibly lost in loss record 1 of 1 ==10818== at 0x400473F: calloc (vg_replace_malloc.c:279) ==10818== by 0x948AA9: _dl_allocate_tls (in /lib/ld-2.5.so) ==10818== by 0xAC8AC8: pthread_create@@GLIBC_2.1 (in /lib/libpthread-2.5.so) ==10818== by 0x819C741: activemq::concurrent::Thread::start() (Thread.cpp:82) ==10818== by 0x805130B: activemq::concurrent::MutexTest::test() (MutexTest.h:422) ==10818== by 0x26D706: CppUnit::TestCaseMethodFunctor::operator()() const (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x25F13D: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x269302: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x269054: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x275C70: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x26D0AC: CppUnit::TestCase::run(CppUnit::TestResult*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x26DD6E: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x26DCA9: CppUnit::TestComposite::run(CppUnit::TestResult*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x26DD6E: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x26DCA9: CppUnit::TestComposite::run(CppUnit::TestResult*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x27811F: CppUnit::TestRunner::WrappingSuite::run(CppUnit::TestResult*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x2758D9: CppUnit::TestResult::runTest(CppUnit::Test*) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x277F5F: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x27B6AA: CppUnit::TextTestRunner::run(CppUnit::TestResult&, std::string const&) (in /usr/lib/libcppunit-1.12.so.0.0.0) ==10818== by 0x27B724: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (in /usr/lib/libcppunit-1.12.so.0.0.0) This is with r487893. > Issues reported by Valgrind when running unit tests > --------------------------------------------------- > > Key: AMQCPP-27 > URL: https://issues.apache.org/activemq/browse/AMQCPP-27 > Project: ActiveMQ C++ Client > Issue Type: Bug > Affects Versions: 1.1 > Reporter: Albert Strasheim > Assigned To: Nathan Mittler > Attachments: activemq-cpp-deletes.diff, activemq-cpp-valgrind.log > > > Valgrind 3.2.1 reported a few issues when running the ActiveMQ C++ unit tests. > Some of them were simple cases of mismatched new[] and delete[] (patch > attached). > Valgrind also reports a few memory leaks, some probably the same as found by > Rational Purify. > Complete Valgrind log attached (after I fixed the deletes). I ran Valgrind as > follows: > valgrind \ > --tool=memcheck \ > --leak-check=yes \ > --error-limit=no \ > --num-callers=20 \ > --freelist-vol=536870912 \ > -v \ > ./activemq-test -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
