Re: [vpp-dev] Vapi causes vpp to crash #vapi
Hi, the issue was caused by a missing memset in shared memory allocation routine. After a few runs, newly allocated message in shared memory would no longer be zero, but random garbage as left over by previous messages, this was then used by vapi_c_test leading to crash. https://gerrit.fd.io/r/c/vpp/+/27472 should be a fix. Thanks, Klement > On 9 Jun 2020, at 16:28, Florin Coras wrote: > > Hi, > > Are you perhaps using a debug vpp image in combination with a release version > of vapi? Debug binaries validate allocations whereas release binaries do not > and do not initialize the allocation’s “magic” field appropriately. So make > sure both binaries are of the same type. > > Regards, > Florin > >> On Jun 8, 2020, at 11:28 PM, carol1311596...@gmail.com wrote: >> >> When I call vapi_cpp_test or vapi_c_test multiple times to test vapi, vpp >> crashes 。 >> >> vpp version : v20.01.1.0-2~g6d190dd >> >> Following is crash gdb session transcript: >> >> Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault. >> 0x76177c0d in ok_magic (m=0xdeaddabe) at >> /data/zj/vpp/src/vppinfra/dlmalloc.c:1623 >> 1623return (m->magic == mparams.magic); >> (gdb) bt >> #0 0x76177c0d in ok_magic (m=0xdeaddabe) at >> /data/zj/vpp/src/vppinfra/dlmalloc.c:1623 >> #1 0x7617fd08 in mspace_free (msp=0x130047010, mem=0x1301c7e40) at >> /data/zj/vpp/src/vppinfra/dlmalloc.c:4489 >> #2 0x7617f232 in mspace_put (msp=0x130047010, p_arg=0x1301c7e44) at >> /data/zj/vpp/src/vppinfra/dlmalloc.c:4321 >> #3 0x77b95304 in clib_mem_free (p=0x1301c7e44) at >> /data/zj/vpp/src/vppinfra/mem.h:238 >> #4 0x77b95df4 in vl_msg_api_free_w_region (vlib_rp=0x130026000, >> a=0x1301c7e54) at /data/zj/vpp/src/vlibmemory/memory_shared.c:306 >> #5 0x77b95e38 in vl_msg_api_free (a=0x1301c7e54) at >> /data/zj/vpp/src/vlibmemory/memory_shared.c:314 >> #6 0x77bc5072 in vl_msg_api_handler_with_vm_node (am=0x77dd5e60 >> , vlib_rp=0x130026000, the_msg=0x1301c7e54, >> vm=0x768ce480 , node=0x7fffb5c23000, >> is_private=0 '\000') at /data/zj/vpp/src/vlibapi/api_shared.c:622 >> #7 0x77b93fb9 in void_mem_api_handle_msg_i (am=0x77dd5e60 >> , vlib_rp=0x130026000, vm=0x768ce480 >> , node=0x7fffb5c23000, is_private=0 '\000') >> at /data/zj/vpp/src/vlibmemory/memory_api.c:698 >> #8 0x77b94005 in vl_mem_api_handle_msg_main (vm=0x768ce480 >> , node=0x7fffb5c23000) at >> /data/zj/vpp/src/vlibmemory/memory_api.c:709 >> #9 0x77bafee6 in vl_api_clnt_process (vm=0x768ce480 >> , node=0x7fffb5c23000, f=0x0) at >> /data/zj/vpp/src/vlibmemory/vlib_api.c:327 >> #10 0x7663103f in vlib_process_bootstrap (_a=140736271608784) at >> /data/zj/vpp/src/vlib/main.c:1475 >> #11 0x760f0240 in clib_calljmp () at >> /data/zj/vpp/src/vppinfra/longjmp.S:123 >> #12 0x7fffb779eba0 in ?? () >> #13 0x76631147 in vlib_process_startup (vm=0x76631aeb >> , p=0x7fffb779eca0, f=0x) at >> /data/zj/vpp/src/vlib/main.c:1497 >> #14 0x189ecf86e039 in ?? () >> #15 0x7fffb5c23000 in ?? () >> #16 0x7fffb65bfb18 in ?? () >> #17 0x7fffb65bf8a8 in ?? () >> #18 0x0018 in ?? () >> #19 0x7fffb65bfb18 in ?? () >> #20 0x7fffb5c23000 in ?? () >> #21 0x7fffb77c6764 in ?? () >> #22 0x in ?? () >> >> >> Thank you in advance! >> > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16703): https://lists.fd.io/g/vpp-dev/message/16703 Mute This Topic: https://lists.fd.io/mt/74769047/21656 Mute #vapi: https://lists.fd.io/g/fdio+vpp-dev/mutehashtag/vapi Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Vapi causes vpp to crash #vapi
Hi, Are you perhaps using a debug vpp image in combination with a release version of vapi? Debug binaries validate allocations whereas release binaries do not and do not initialize the allocation’s “magic” field appropriately. So make sure both binaries are of the same type. Regards, Florin > On Jun 8, 2020, at 11:28 PM, carol1311596...@gmail.com wrote: > > When I call vapi_cpp_test or vapi_c_test multiple times to test vapi, vpp > crashes 。 > > vpp version : v20.01.1.0-2~g6d190dd > > Following is crash gdb session transcript: > > Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault. > 0x76177c0d in ok_magic (m=0xdeaddabe) at > /data/zj/vpp/src/vppinfra/dlmalloc.c:1623 > 1623return (m->magic == mparams.magic); > (gdb) bt > #0 0x76177c0d in ok_magic (m=0xdeaddabe) at > /data/zj/vpp/src/vppinfra/dlmalloc.c:1623 > #1 0x7617fd08 in mspace_free (msp=0x130047010, mem=0x1301c7e40) at > /data/zj/vpp/src/vppinfra/dlmalloc.c:4489 > #2 0x7617f232 in mspace_put (msp=0x130047010, p_arg=0x1301c7e44) at > /data/zj/vpp/src/vppinfra/dlmalloc.c:4321 > #3 0x77b95304 in clib_mem_free (p=0x1301c7e44) at > /data/zj/vpp/src/vppinfra/mem.h:238 > #4 0x77b95df4 in vl_msg_api_free_w_region (vlib_rp=0x130026000, > a=0x1301c7e54) at /data/zj/vpp/src/vlibmemory/memory_shared.c:306 > #5 0x77b95e38 in vl_msg_api_free (a=0x1301c7e54) at > /data/zj/vpp/src/vlibmemory/memory_shared.c:314 > #6 0x77bc5072 in vl_msg_api_handler_with_vm_node (am=0x77dd5e60 > , vlib_rp=0x130026000, the_msg=0x1301c7e54, > vm=0x768ce480 , node=0x7fffb5c23000, > is_private=0 '\000') at /data/zj/vpp/src/vlibapi/api_shared.c:622 > #7 0x77b93fb9 in void_mem_api_handle_msg_i (am=0x77dd5e60 > , vlib_rp=0x130026000, vm=0x768ce480 , > node=0x7fffb5c23000, is_private=0 '\000') > at /data/zj/vpp/src/vlibmemory/memory_api.c:698 > #8 0x77b94005 in vl_mem_api_handle_msg_main (vm=0x768ce480 > , node=0x7fffb5c23000) at > /data/zj/vpp/src/vlibmemory/memory_api.c:709 > #9 0x77bafee6 in vl_api_clnt_process (vm=0x768ce480 > , node=0x7fffb5c23000, f=0x0) at > /data/zj/vpp/src/vlibmemory/vlib_api.c:327 > #10 0x7663103f in vlib_process_bootstrap (_a=140736271608784) at > /data/zj/vpp/src/vlib/main.c:1475 > #11 0x760f0240 in clib_calljmp () at > /data/zj/vpp/src/vppinfra/longjmp.S:123 > #12 0x7fffb779eba0 in ?? () > #13 0x76631147 in vlib_process_startup (vm=0x76631aeb > , p=0x7fffb779eca0, f=0x) at > /data/zj/vpp/src/vlib/main.c:1497 > #14 0x189ecf86e039 in ?? () > #15 0x7fffb5c23000 in ?? () > #16 0x7fffb65bfb18 in ?? () > #17 0x7fffb65bf8a8 in ?? () > #18 0x0018 in ?? () > #19 0x7fffb65bfb18 in ?? () > #20 0x7fffb5c23000 in ?? () > #21 0x7fffb77c6764 in ?? () > #22 0x in ?? () > > > Thank you in advance! > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16702): https://lists.fd.io/g/vpp-dev/message/16702 Mute This Topic: https://lists.fd.io/mt/74769047/21656 Mute #vapi: https://lists.fd.io/g/fdio+vpp-dev/mutehashtag/vapi Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Vapi causes vpp to crash #vapi
When I call *vapi_cpp_test or* vapi_c_test multiple times to test vapi, vpp crashes 。 vpp version : v20.01.1.0-2~g6d190dd Following is crash gdb session transcript: Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault. 0x76177c0d in ok_magic (m=0xdeaddabe) at /data/zj/vpp/src/vppinfra/dlmalloc.c:1623 1623 return (m->magic == mparams.magic); (gdb) bt #0 0x76177c0d in ok_magic (m=0xdeaddabe) at /data/zj/vpp/src/vppinfra/dlmalloc.c:1623 #1 0x7617fd08 in mspace_free (msp=0x130047010, mem=0x1301c7e40) at /data/zj/vpp/src/vppinfra/dlmalloc.c:4489 #2 0x7617f232 in mspace_put (msp=0x130047010, p_arg=0x1301c7e44) at /data/zj/vpp/src/vppinfra/dlmalloc.c:4321 #3 0x77b95304 in clib_mem_free (p=0x1301c7e44) at /data/zj/vpp/src/vppinfra/mem.h:238 #4 0x77b95df4 in vl_msg_api_free_w_region (vlib_rp=0x130026000, a=0x1301c7e54) at /data/zj/vpp/src/vlibmemory/memory_shared.c:306 #5 0x77b95e38 in vl_msg_api_free (a=0x1301c7e54) at /data/zj/vpp/src/vlibmemory/memory_shared.c:314 #6 0x77bc5072 in vl_msg_api_handler_with_vm_node (am=0x77dd5e60 , vlib_rp=0x130026000, the_msg=0x1301c7e54, vm=0x768ce480 , node=0x7fffb5c23000, is_private=0 '\000') at /data/zj/vpp/src/vlibapi/api_shared.c:622 #7 0x77b93fb9 in void_mem_api_handle_msg_i (am=0x77dd5e60 , vlib_rp=0x130026000, vm=0x768ce480 , node=0x7fffb5c23000, is_private=0 '\000') at /data/zj/vpp/src/vlibmemory/memory_api.c:698 #8 0x77b94005 in vl_mem_api_handle_msg_main (vm=0x768ce480 , node=0x7fffb5c23000) at /data/zj/vpp/src/vlibmemory/memory_api.c:709 #9 0x77bafee6 in vl_api_clnt_process (vm=0x768ce480 , node=0x7fffb5c23000, f=0x0) at /data/zj/vpp/src/vlibmemory/vlib_api.c:327 #10 0x7663103f in vlib_process_bootstrap (_a=140736271608784) at /data/zj/vpp/src/vlib/main.c:1475 #11 0x760f0240 in clib_calljmp () at /data/zj/vpp/src/vppinfra/longjmp.S:123 #12 0x7fffb779eba0 in ?? () #13 0x76631147 in vlib_process_startup (vm=0x76631aeb , p=0x7fffb779eca0, f=0x) at /data/zj/vpp/src/vlib/main.c:1497 #14 0x189ecf86e039 in ?? () #15 0x7fffb5c23000 in ?? () #16 0x7fffb65bfb18 in ?? () #17 0x7fffb65bf8a8 in ?? () #18 0x0018 in ?? () #19 0x7fffb65bfb18 in ?? () #20 0x7fffb5c23000 in ?? () #21 0x7fffb77c6764 in ?? () #22 0x in ?? () Thank you in advance! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16698): https://lists.fd.io/g/vpp-dev/message/16698 Mute This Topic: https://lists.fd.io/mt/74769047/21656 Mute #vapi: https://lists.fd.io/g/fdio+vpp-dev/mutehashtag/vapi Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
