Kim van der Riet created PROTON-2274:
----------------------------------------
Summary: Threaderciser test valgrind error
Key: PROTON-2274
URL: https://issues.apache.org/jira/browse/PROTON-2274
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Reporter: Kim van der Riet
A recent test of Proton [1] revealed a threadersiser valgrind error:
{noformat}
test 7
Start 7: c-threaderciser
7: Test command: /opt/pyenv/shims/python3
"/home/travis/build/apache/qpid-proton/scripts/env.py" "--"
"TEST_EXE_PREFIX=/usr/bin/valgrind --tool=memcheck --leak-check=full
--error-exitcode=42 --quiet
--suppressions=/home/travis/build/apache/qpid-proton/tests/valgrind.supp"
"/usr/bin/valgrind" "--tool=memcheck" "--leak-check=full" "--error-exitcode=42"
"--quiet"
"--suppressions=/home/travis/build/apache/qpid-proton/tests/valgrind.supp"
"/home/travis/build/apache/qpid-proton/build/c/tests/c-threaderciser"
7: Test timeout computed to be: 360
7: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
connect, close-connect, wake, timeout, cancel-timeout]
7: ==12926== 128,678 (1,128 direct, 127,550 indirect) bytes in 1 blocks are
definitely lost in loss record 165 of 165
7: ==12926== at 0x483B7F3: malloc (in
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
7: ==12926== by 0x10B110: listener_ctx_new (threaderciser.c:264)
7: ==12926== by 0x10B110: lpool_listen.part.0 (threaderciser.c:283)
7: ==12926== by 0x10B88B: lpool_listen (threaderciser.c:380)
7: ==12926== by 0x10B88B: global_do_stuff (threaderciser.c:380)
7: ==12926== by 0x10BBD7: user_thread (threaderciser.c:398)
7: ==12926== by 0x48AF608: start_thread (pthread_create.c:477)
7: ==12926== by 0x49EB102: clone (clone.S:95)
7: ==12926==
7/48 Test #7: c-threaderciser ..................***Failed 2.14 sec
{noformat}
[1] [https://travis-ci.org/github/apache/qpid-proton/jobs/721459983]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
