jermus67 opened a new issue #308: URL: https://github.com/apache/celix/issues/308
Hello, Compiling celix on the Raspberry Pi 400 went almost without problems. For some sprintf() statements, because of the "%lu" formatting, a cast had to be added to (long unsigned int) for size_t parameters. The Raspberry Pi 400 is installed with Raspberry Pi OS (32-bit), in which size_t is an unsigned int, not a long unsigned int, hence the upcast. However, of all the 40 tests 22 do not pass (see end of post for the complete list of failing tests). This is the first of them: pi@raspberrypi:~/Projects/celix/cmake-build-debug/libs/utils $ gdb array_list_testd GNU gdb (Raspbian 8.2.1-2) 8.2.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabihf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from array_list_testd...done. (gdb) run Starting program: /home/pi/Projects/celix/cmake-build-debug/libs/utils/array_list_testd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". ..................realloc(): invalid next size Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0xb6c0d230 in __GI_abort () at abort.c:79 #2 0xb6c5d51c in __libc_message (action=action@entry=do_abort, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:181 #3 0xb6c64044 in malloc_printerr (str=<optimized out>) at malloc.c:5341 #4 0xb6c68a20 in _int_realloc (av=av@entry=0xb6d407d4 <main_arena>, oldp=oldp@entry=0x4c4b8, oldsize=oldsize@entry=48, nb=nb@entry=72) at malloc.c:4561 #5 0xb6c69c50 in __GI___libc_realloc (oldmem=0x4c4c0, bytes=64) at malloc.c:3213 #6 0xb6f9b688 in arrayList_ensureCapacity (list=0x4c4a0, capacity=11) at /home/pi/Projects/celix/libs/utils/src/array_list.c:97 #7 0xb6f9bacc in arrayList_add (list=0x4c4a0, element=0x4caf8) at /home/pi/Projects/celix/libs/utils/src/array_list.c:185 #8 0x000126b8 in TEST_array_list_clone_Test::testBody (this=0x4c490) at /home/pi/Projects/celix/libs/utils/private/test/array_list_test.cpp:131 #9 0x00029340 in PlatformSpecificSetJmpImplementation () #10 0x00026f58 in Utest::run() () #11 0x00028d70 in UtestShell::runOneTestInCurrentProcess(TestPlugin*, TestResult&) () #12 0x00029340 in PlatformSpecificSetJmpImplementation () #13 0x00027064 in UtestShell::runOneTest(TestPlugin*, TestResult&) () #14 0x00026690 in TestRegistry::runAllTests(TestResult&) () #15 0x0001bce0 in CommandLineTestRunner::runAllTests() () #16 0x0001bdc8 in CommandLineTestRunner::runAllTestsMain() () #17 0x0001bef0 in CommandLineTestRunner::RunAllTests(int, char const**) () #18 0x00011efc in main (argc=1, argv=0xbefff2c4) at /home/pi/Projects/celix/libs/utils/private/test/array_list_test.cpp:45 (gdb) A little more info: pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux I have tried to run the test with valgrind (valgrind-1:3.7.0-6-rpi6), but that results in a never ending, very busy, process (100% cpu-load on one core). I'll attach the output (for what it's worth...) : [valgrind_output_3576.txt](https://github.com/apache/celix/files/5655300/valgrind_output_3576.txt) I'll be looking into this myself too, but I thought it might be good to report this issue. Maybe someone knows how to fix this. At the time of writing I still don't. Kind regards, Jeroen Kouwer --- pi@raspberrypi:~/Projects/celix/cmake-build-debug $ make test Running tests... Test project /home/pi/Projects/celix/cmake-build-debug Start 1: run_array_list_test 1/40 Test #1: run_array_list_test .................Subprocess aborted***Exception: 0.01 sec Start 2: run_hash_map_test 2/40 Test #2: run_hash_map_test ................... Passed 0.02 sec Start 3: run_celix_threads_test 3/40 Test #3: run_celix_threads_test .............. Passed 10.02 sec Start 4: run_linked_list_test 4/40 Test #4: run_linked_list_test ................ Passed 0.02 sec Start 5: run_properties_test 5/40 Test #5: run_properties_test ................. Passed 0.01 sec Start 6: run_utils_test 6/40 Test #6: run_utils_test ...................... Passed 0.02 sec Start 7: run_ip_utils_test 7/40 Test #7: run_ip_utils_test ................... Passed 0.01 sec Start 8: filter_test 8/40 Test #8: filter_test ......................... Passed 0.02 sec Start 9: version_range_test 9/40 Test #9: version_range_test .................. Passed 0.02 sec Start 10: version_test 10/40 Test #10: version_test ........................ Passed 0.01 sec Start 11: test_utils 11/40 Test #11: test_utils .......................... Passed 0.02 sec Start 12: run_test_dfi 12/40 Test #12: run_test_dfi ........................***Exception: SegFault 0.06 sec Start 13: test_framework 13/40 Test #13: test_framework ......................Subprocess aborted***Exception: 0.09 sec Start 14: run_test_tm_scoped 14/40 Test #14: run_test_tm_scoped ..................***Exception: SegFault 0.09 sec Start 15: run_test_rsa_dfi 15/40 Test #15: run_test_rsa_dfi ....................Subprocess terminated***Exception: 11.45 sec Start 16: http_websocket_tests 16/40 Test #16: http_websocket_tests ................***Exception: SegFault 1.09 sec Start 17: test_shell 17/40 Test #17: test_shell ..........................***Exception: SegFault 0.08 sec Start 18: test_log_helper 18/40 Test #18: test_log_helper ..................... Passed 0.05 sec Start 19: test_log_admin 19/40 Test #19: test_log_admin ......................Subprocess aborted***Exception: 0.05 sec Start 20: test_syslog_writer 20/40 Test #20: test_syslog_writer .................. Passed 0.06 sec Start 21: test_pubsub_utils 21/40 Test #21: test_pubsub_utils ...................Subprocess terminated***Exception: 11.52 sec Start 22: test_pubsub_serializer_json 22/40 Test #22: test_pubsub_serializer_json ......... Passed 0.07 sec Start 23: test_pubsub_serializer_avrobin 23/40 Test #23: test_pubsub_serializer_avrobin ...... Passed 0.06 sec Start 24: celix_pswp_common_tests 24/40 Test #24: celix_pswp_common_tests ............. Passed 0.66 sec Start 25: celix_pswp_tests 25/40 Test #25: celix_pswp_tests .................... Passed 0.04 sec Start 26: celix_pswp_v2_tests 26/40 Test #26: celix_pswp_v2_tests ................. Passed 0.04 sec Start 27: pubsubmock_test 27/40 Test #27: pubsubmock_test ..................... Passed 0.03 sec Start 28: pstm_deadlock_udpmc_test 28/40 Test #28: pstm_deadlock_udpmc_test ............Subprocess aborted***Exception: 0.07 sec Start 29: pubsub_tcp_tests 29/40 Test #29: pubsub_tcp_tests ....................Subprocess aborted***Exception: 0.06 sec Start 30: pstm_deadlock_tcp_test 30/40 Test #30: pstm_deadlock_tcp_test ..............Subprocess aborted***Exception: 0.06 sec Start 31: pubsub_websocket_tests 31/40 Test #31: pubsub_websocket_tests ..............Subprocess aborted***Exception: 0.07 sec Start 32: pstm_deadlock_websocket_test 32/40 Test #32: pstm_deadlock_websocket_test ........Subprocess aborted***Exception: 0.06 sec Start 33: pubsub_zmq_tests 33/40 Test #33: pubsub_zmq_tests ....................Subprocess aborted***Exception: 0.08 sec Start 34: pubsub_zmq_v2_tests 34/40 Test #34: pubsub_zmq_v2_tests .................Subprocess aborted***Exception: 0.07 sec Start 35: pubsub_zmq_wire_v2_tests 35/40 Test #35: pubsub_zmq_wire_v2_tests ............Subprocess aborted***Exception: 0.06 sec Start 36: pubsub_zmq_zerocopy_tests 36/40 Test #36: pubsub_zmq_zerocopy_tests ...........Subprocess aborted***Exception: 0.06 sec Start 37: pubsub_zmq_v2_zerocopy_tests 37/40 Test #37: pubsub_zmq_v2_zerocopy_tests ........Subprocess aborted***Exception: 0.06 sec Start 38: pubsub_zmq_zerocopy_wire_v2_tests 38/40 Test #38: pubsub_zmq_zerocopy_wire_v2_tests ...Subprocess aborted***Exception: 0.06 sec Start 39: pstm_deadlock_zmq_test 39/40 Test #39: pstm_deadlock_zmq_test ..............Subprocess aborted***Exception: 0.07 sec Start 40: pstm_deadlock_zmq_v2_test 40/40 Test #40: pstm_deadlock_zmq_v2_test ...........Subprocess aborted***Exception: 0.07 sec 45% tests passed, 22 tests failed out of 40 Total Test time (real) = 36.55 sec The following tests FAILED: 1 - run_array_list_test (Subprocess aborted) 12 - run_test_dfi (SEGFAULT) 13 - test_framework (Subprocess aborted) 14 - run_test_tm_scoped (SEGFAULT) 15 - run_test_rsa_dfi (Subprocess terminated) 16 - http_websocket_tests (SEGFAULT) 17 - test_shell (SEGFAULT) 19 - test_log_admin (Subprocess aborted) 21 - test_pubsub_utils (Subprocess terminated) 28 - pstm_deadlock_udpmc_test (Subprocess aborted) 29 - pubsub_tcp_tests (Subprocess aborted) 30 - pstm_deadlock_tcp_test (Subprocess aborted) 31 - pubsub_websocket_tests (Subprocess aborted) 32 - pstm_deadlock_websocket_test (Subprocess aborted) 33 - pubsub_zmq_tests (Subprocess aborted) 34 - pubsub_zmq_v2_tests (Subprocess aborted) 35 - pubsub_zmq_wire_v2_tests (Subprocess aborted) 36 - pubsub_zmq_zerocopy_tests (Subprocess aborted) 37 - pubsub_zmq_v2_zerocopy_tests (Subprocess aborted) 38 - pubsub_zmq_zerocopy_wire_v2_tests (Subprocess aborted) 39 - pstm_deadlock_zmq_test (Subprocess aborted) 40 - pstm_deadlock_zmq_v2_test (Subprocess aborted) Errors while running CTest make: *** [Makefile:126: test] Error 8 The tests that report "Subprocess terminated***Exception" were manually killed, because they went into highload. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
