ThreadPoolTest fails when run under Valgrind 2.4.0 on Fedora Core 4
-------------------------------------------------------------------
Key: AMQCPP-97
URL: https://issues.apache.org/activemq/browse/AMQCPP-97
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 2.0
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Priority: Minor
Fix For: 2.0
The unit tests fail when run under Valgrind 2.4.0 on Fedora Core 4 with the
following output:
activemq::concurrent::ThreadPoolTest::test1. : errorE
activemq::concurrent::ThreadPoolTest::test2terminate called after throwing an
instance of 'activemq::exceptions::ActiveMQException'
what(): Thread::join() called without having called Thread::start()
.==9261==
==9261== Process terminating with default action of signal 6 (SIGABRT)
==9261== at 0x59FF90: raise (in /lib/libc-2.3.6.so)
==9261== by 0x5A1677: abort (in /lib/libc-2.3.6.so)
==9261== by 0x29E483: __gnu_cxx::__verbose_terminate_handler() (in
/usr/lib/libstdc++.so.6.0.7)
==9261== by 0x29C114: (within /usr/lib/libstdc++.so.6.0.7)
==9261== by 0x29C0E1: __gxx_personality_v0 (in /usr/lib/libstdc++.so.6.0.7)
==9261== by 0x75BFD6: (within /lib/libgcc_s-4.0.2-20051126.so.1)
==9261== by 0x75C090: _Unwind_Resume (in /lib/libgcc_s-4.0.2-20051126.so.1)
==9261== by 0x81C83E1: activemq::concurrent::ThreadPool::~ThreadPool()
(PooledThreadListener.h:34)
==9261== by 0x8056DB6: activemq::concurrent::ThreadPoolTest::test2()
(ThreadPoolTest.h:195)
==9261== by 0xD31555: CppUnit::TestCaseMethodFunctor::operator()() const (in
/usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD20507: CppUnit::DefaultProtector::protect(CppUnit::Functor
const&, CppUnit::ProtectorContext const&) (in /usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD2ACDC: CppUnit::ProtectorChain::ProtectFunctor::operator()()
const (in /usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD2A85B: CppUnit::ProtectorChain::protect(CppUnit::Functor
const&, CppUnit::ProtectorContext const&) (in /usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD3CA60: CppUnit::TestResult::protect(CppUnit::Functor const&,
CppUnit::Test*, std::string const&) (in /usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD3087F: CppUnit::TestCase::run(CppUnit::TestResult*) (in
/usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD31D72:
CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (in
/usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD31C6D: CppUnit::TestComposite::run(CppUnit::TestResult*) (in
/usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD31D72:
CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (in
/usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD31C6D: CppUnit::TestComposite::run(CppUnit::TestResult*) (in
/usr/lib/libcppunit-1.11.so.0.0.0)
==9261== by 0xD41BC3:
CppUnit::TestRunner::WrappingSuite::run(CppUnit::TestResult*) (in
/usr/lib/libcppunit-1.11.so.0.0.0)
Maybe the test code is thrown off by the longer time it takes to run when
executing with Valgrind.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
