This seems consistent with a SIGSEGV compounded by a worker-thread stack
overflow situation. In hopes of obtaining a clean core file, you might want to
modify the SIGSEGV handler to simply abort() instead of trying to write a
post-mortem API dump, syslog’ing a backtrace, etc.
Best of luck wi
Hi ， Stanislav Zaikin
May be memroy overwrite issue, especial vlib buffer. Becasue VPP use vector
packet processing, not scalar packet processing, so you can see
a unexpected nodes even if not a stack corrupted .
You can use debug version with CLIB_DEBUG>0 to location the root cause.
