Hi Raj, 

We removed udpc transport in vpp. I’ll push a patch that removes it from vcl as 
well. 

Calling connect on a udp connection will give you connected semantics now. Let 
me know if that solves the issue for you.

Regards,
Florin


> On May 15, 2020, at 12:15 PM, Raj Kumar <raj.gauta...@gmail.com> wrote:
> 
> Hi,
> I am getting segmentation fault in VPP when using VCL VPPCOM_PROTO_UDPC  
> socket. This issue is observed with both UDP sender and UDP receiver 
> application.
> 
> However, both UDP sender and receiver works fine with VPPCOM_PROTO_UDP.
> 
> Here is the stack trace - 
> 
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x00007ffff775da59 in session_open_vc (app_wrk_index=1, 
> rmt=0x7fffb5e34cc0, opaque=0)
>     at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vnet/session/session.c:1217
> #2  0x00007ffff7779257 in session_mq_connect_handler (data=0x7fffb676e7a8)
>     at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vnet/session/session_node.c:138
> #3  0x00007ffff7780f48 in session_event_dispatch_ctrl (elt=0x7fffb643f51c, 
> wrk=0x7fffb650a640)
>     at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vnet/session/session.h:262
> #4  session_queue_node_fn (vm=<optimized out>, node=<optimized out>, 
> frame=<optimized out>)
>     at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vnet/session/session_node.c:1409
> #5  0x00007ffff6b214c1 in dispatch_node (last_time_stamp=<optimized out>, 
> frame=0x0, dispatch_state=VLIB_NODE_STATE_POLLING,
>     type=VLIB_NODE_TYPE_INPUT, node=0x7fffb5a9a980, vm=0x7ffff6d7c200 
> <vlib_global_main>)
>     at /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vlib/main.c:1235
> #6  vlib_main_or_worker_loop (is_main=1, vm=0x7ffff6d7c200 <vlib_global_main>)
>     at /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vlib/main.c:1815
> #7  vlib_main_loop (vm=0x7ffff6d7c200 <vlib_global_main>) at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vlib/main.c:1990
> #8  vlib_main (vm=<optimized out>, vm@entry=0x7ffff6d7c200 
> <vlib_global_main>, input=input@entry=0x7fffb5e34fa0)
>     at /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vlib/main.c:2236
> #9  0x00007ffff6b61756 in thread0 (arg=140737334723072) at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vlib/unix/main.c:658
> #10 0x00007ffff602fc0c in clib_calljmp () from /lib64/libvppinfra.so.20.05
> #11 0x00007fffffffd1e0 in ?? ()
> #12 0x00007ffff6b627ed in vlib_unix_main (argc=<optimized out>, 
> argv=<optimized out>)
>     at 
> /usr/src/debug/vpp-20.05-rc0~748_g83d129837.x86_64/src/vlib/unix/main.c:730
> 
> Earlier , I tested this functionality with VPP 20.01 release with the 
> following patches and it worked perfectly.
> https://gerrit.fd.io/r/c/vpp/+/24332 <https://gerrit.fd.io/r/c/vpp/+/24332>
> https://gerrit.fd.io/r/c/vpp/+/24334 <https://gerrit.fd.io/r/c/vpp/+/24334>
> https://gerrit.fd.io/r/c/vpp/+/24462 <https://gerrit.fd.io/r/c/vpp/+/24462>
> 
> Thanks,
> -Raj
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16414): https://lists.fd.io/g/vpp-dev/message/16414
Mute This Topic: https://lists.fd.io/mt/74234856/21656
Mute #vpp-hoststack: https://lists.fd.io/mk?hashtag=vpp-hoststack&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to