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
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
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/sr
