t...
D.
From: xulang
Sent: Friday, May 25, 2018 11:15 PM
To: Dave Barach (dbarach)
Cc:vpp-dev@lists.fd.io
Subject: Re:RE: [vpp-dev] new next_node caused Segmentation fault
yeah, ~0 is not right,
but I only changed "ip_local_next_t" and "VLIB_REGISTER_NODE (ip4_local_
@lists.fd.io
Subject: Re:RE: [vpp-dev] new next_node caused Segmentation fault
yeah, ~0 is not right,
but I only changed "ip_local_next_t" and "VLIB_REGISTER_NODE (ip4_local_node)"
This is backtrace.
(gdb) bt
#0 0x7776e73d in vlib_get_node (i=4294967295,
vm=0x7
vpp-dev@lists.fd.io On Behalf Of xulang
Sent: Friday, May 25, 2018 5:27 AM
To:vpp-dev@lists.fd.io
Subject: [vpp-dev] new next_node caused Segmentation fault
Hi all,
I tried to add a new next node to the node "ip4_local_node",
but which caused a segmentation fault, is there s
Of xulang
Sent: Friday, May 25, 2018 5:27 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] new next_node caused Segmentation fault
Hi all,
I tried to add a new next node to the node "ip4_local_node",
but which caused a segmentation fault, is there something I have missed?
ty
Hi all,
I tried to add a new next node to the node "ip4_local_node",
but which caused a segmentation fault, is there something I have missed?
typedef enum
{
IP_LOCAL_NEXT_DROP,
IP_LOCAL_NEXT_PUNT,
IP_LOCAL_NEXT_UDP_LOOKUP,
IP_LOCAL_NEXT_ICMP,
IP_LOCAL_NEXT_CAPWAP,
IP_LOCAL_N_NEXT,
}
