Hi Dom, You can’t run app debug binaries against vpp release binaries because dlmalloc will try to validate allocations between two processes. That’s the crash you got lower. Try to run vpp debug binaries with tcp_echo debug binaries.
Most of our testing is based on vcl (say with iperf[1]). Does that work okay for you? Florin [1] https://wiki.fd.io/view/VPP/HostStack/LDP/iperf > On Nov 22, 2019, at 10:30 AM, dch...@akouto.com wrote: > > Hello, > > I'm trying to run a simple test using the tcp_echo application using > 19.08.1-release, but it just crashes pretty early on. I built a debug version > and tried to debug the crash that happens in mspace_malloc: > > void* mspace_malloc(mspace msp, size_t bytes) { > mstate ms = (mstate)msp; > if (!ok_magic(ms)) { > USAGE_ERROR_ACTION(ms,ms); > return 0; > } > > The call to ok_magic returns 0 and the program exits. Stepping through the > code, the issue happens while still trying to connect to VPP at > initialization: > > Thrd #1 [tcp_echo] 5012 [core: 1] (Suspended : Signal : SIGABRT:Aborted) > __GI_raise() at raise.c:55 0x7ffff6bb7337 > __GIea_abort() at abort.c:90 0x7ffff6bb8a28 > os_panic() at unix-misc.c:176 0x7ffff773fd77 > mspace_malloc() at dlmalloc.c:4,344 0x7ffff775ca4b > mspace_get_aligned() at dlmalloc.c:4,233 0x7ffff775c7cc > clib_mem_alloc_aligned_at_offset() at mem.h:139 0x7ffff7748c7b > vec_resize_allocate_memory() at vec.c:59 0x7ffff7748ec6 > _vec_resize_inline() at vec.h:147 0x7ffff76b6e54 > do_percent() at format.c:341 0x7ffff76b7e09 > va_format() at format.c:404 0x7ffff76b828d > format() at format.c:428 0x7ffff76b8400 > shm_name_from_svm_map_region_args() at svm.c:456 0x7ffff79a07d5 > svm_map_region() at svm.c:593 0x7ffff79a0fe9 > svm_region_find_or_create() at svm.c:931 0x7ffff79a2050 > vl_map_shmem() at memory_shared.c:605 0x7ffff7bbe4b2 > vl_client_api_map() at memory_client.c:371 0x7ffff7bc1225 > connect_to_vlib_internal() at memory_client.c:398 0x7ffff7bc129f > vl_client_connect_to_vlib() at memory_client.c:429 0x7ffff7bc1396 > connect_to_vpp() at tcp_echo.c:436 0x40b291 > main() at tcp_echo.c:1,389 0x40f723 > > The internal test echo client/server work fine, so I think I've set things up > correctly but I'm not sure if I'm missing something for the external > client/server, or if they work for everyone else on 19.08.1-release. > > All I do is bring up VPP, set an IP address on the interface, and then run > the tcp_echo application. Can someone please let me know if the tcp_echo > application works for them on 19.08.1-release, and if so are there any other > steps needed for it to run other than what I've mentioned? > > Thank you in advance! > > Dom > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#14672): https://lists.fd.io/g/vpp-dev/message/14672 > Mute This Topic: https://lists.fd.io/mt/61720535/675152 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [fcoras.li...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14674): https://lists.fd.io/g/vpp-dev/message/14674 Mute This Topic: https://lists.fd.io/mt/61720535/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
