[
https://issues.apache.org/jira/browse/ZOOKEEPER-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711787#action_12711787
]
Mahadev konar commented on ZOOKEEPER-415:
-
the stack traces are -
- thread 1
{code}
0 0x003f41e075a5 in pthread_join () from /lib64/libpthread.so.0
#1 0x0044cef4 in pthread_join (t=1075841344, r=0x0) at
zootestbuild/trunk/src/c/tests/PthreadMocks.cc:70
#2 0x004591ce in adaptor_finish (zh=0x2c0024d0) at
zootestbuild/trunk/src/c/src/mt_adaptor.c:218
#3 0x0045066e in zookeeper_close (zh=0x2c0024d0) at
zootestbuild/trunk/src/c/src/zookeeper.c:1870
#4 0x0044856b in ~watchCtx (this=0x7fff244a1290) at
zootestbuild/trunk/src/c/tests/TestClient.cc:111
#5 0x00448675 in Zookeeper_simpleSystem::testWatcherAutoResetWithLocal
(this=0x12450330) at zootestbuild/trunk/src/c/tests/TestClient.cc:671
#6 0x004403d6 in CppUnit::TestCallerZookeeper_simpleSystem::runTest
(this=0x12450350) at /usr/local/include/cppunit/TestCaller.h:166
#7 0x2aaef2bf in CppUnit::TestCaseMethodFunctor::operator()
(this=0x402009d0) at TestCase.cpp:32
#8 0x2aadc664 in CppUnit::DefaultProtector::protect (this=0x1244db80,
funct...@0x402009d0, conte...@0x7fff244a1680) at DefaultProtector.cpp:15
#9 0x2aaeb049 in CppUnit::ProtectorChain::ProtectFunctor::operator()
(this=0x402009d0) at ProtectorChain.cpp:20
#10 0x2aaeac3f in CppUnit::ProtectorChain::protect (this=0x1244d8c0,
funct...@0x7fff244a16e0, conte...@0x7fff244a1680) at ProtectorChain.cpp:77
#11 0x2aafb964 in CppUnit::TestResult::protect (this=0x7fff244a1a00,
funct...@0x7fff244a16e0, test=0x31f3, shortdescripti...@0x0) at
TestResult.cpp:178
#12 0x2aaeefb4 in CppUnit::TestCase::run (this=0x12450350,
result=0x7fff244a1a00) at TestCase.cpp:27
#13 0x2aaef869 in CppUnit::TestComposite::doRunChildTests
(this=0x1244fb70, controller=0x7fff244a1a00) at TestComposite.cpp:64
#14 0x2aaef776 in CppUnit::TestComposite::run (this=0x1244fb70,
result=0x7fff244a1a00) at TestComposite.cpp:23
#15 0x2aaef869 in CppUnit::TestComposite::doRunChildTests
(this=0x1244e110, controller=0x7fff244a1a00) at TestComposite.cpp:64
#16 0x2aaef776 in CppUnit::TestComposite::run (this=0x1244e110,
result=0x7fff244a1a00) at TestComposite.cpp:23
#17 0x2aafb8da in CppUnit::TestResult::runTest (this=0x7fff244a1a00,
test=0x1244e0b0) at TestResult.cpp:145
#18 0x2aaff705 in CppUnit::TestRunner::run (this=0x402009d0,
controll...@0x7fff244a1a00, testpa...@0x31f3) at TestRunner.cpp:96
#19 0x004059e1 in main (argc=1, argv=0x7fff244a1bd8) at
zootestbuild/trunk/src/c/tests/TestDriver.cc:91
{code}
- thread 2
{code}
#0 0x003f41e0c878 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
#1 0x003f41e088a5 in _L_mutex_lock_107 () from /lib64/libpthread.so.0
#2 0x003f41e08333 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3 0x0041096e in Mutex::acquire (this=0x7fff244a1280) at
zootestbuild/trunk/src/c/tests/ThreadingUtil.cc:40
#4 0x00442121 in watchCtx::putEvent (this=0x7fff244a1260,
e...@0x401ffea0) at zootestbuild/trunk/src/c/tests/TestClient.cc:134
#5 0x004421c3 in Zookeeper_simpleSystem::watcher (type=1, state=3,
path=0x12459e80 /watchtest/child2, v=0x7fff244a1260)
at zootestbuild/trunk/src/c/tests/TestClient.cc:181
#6 0x00458338 in deliverWatchers (zh=0x2c0024d0, type=1, state=3,
path=0x12459e80 /watchtest/child2, list=0x12456ad8)
at zootestbuild/trunk/src/c/src/zk_hashtable.c:270
#7 0x0040ca9e in __wrap_deliverWatchers (zh=0x2c0024d0, type=1,
state=3, path=0x12459e80 /watchtest/child2, list=0x12456ad8)
at zootestbuild/trunk/src/c/tests/ZKMocks.cc:218
#8 0x00450ab8 in process_completions (zh=0x2c0024d0) at
zootestbuild/trunk/src/c/src/zookeeper.c:1407
#9 0x00458af1 in do_completion (v=value optimized out) at
zootestbuild/trunk/src/c/src/mt_adaptor.c:332
#10 0x003f41e062e7 in start_thread () from /lib64/libpthread.so.0
#11 0x003f412ce3bd in clone () from /lib64/libc.so.6
{code}
zookeeper c tests hang.
---
Key: ZOOKEEPER-415
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-415
Project: Zookeeper
Issue Type: Bug
Reporter: Mahadev konar
Assignee: Mahadev konar
Fix For: 3.2.0
the c tests hang sometimes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
