[dpdk-users] Segmentation fault in rte_eth_devices()

David Aldrich david.aldrich.ntml at gmail.com
Wed Jun 10 18:28:07 CEST 2020


Hi,

I am building an app based on dpdk-stable-18.11.8. I am seeing a
segmentation fault in my call to rte_eth_rx_burst(). I ran gdb on the core
dump and I see:

#0  0x0000000000f65680 in rte_eth_devices ()
#1  0x000000000048a03a in rte_eth_rx_burst (nb_pkts=7,
rx_pkts=0x7fab40620480, queue_id=0, port_id=<optimized out>)
    at
/opt/dpdk/dpdk-18.08/x86_64-native-linuxapp-gcc/include/rte_ethdev.h:3825
#2  Socket_poll (ucRxPortId=<optimized out>, ucRxQueId=ucRxQueId at entry=0
'\000', uiMaxNumOfRxFrm=uiMaxNumOfRxFrm at entry=7,
    pISocketListener=pISocketListener at entry=0xf635d0 <FH_gtFrontHaulObj+16>)
    at /data/<snip>/SocketClass.c:2188
#3  0x000000000048b941 in FH_perform (args_ptr=<optimized out>) at
/data/<snip>/FrontHaul.c:281
#4  0x00000000005788e4 in eal_thread_loop ()
#5  0x00007fab419fae65 in start_thread () from /lib64/libpthread.so.0
#6  0x00007fab4172388d in clone () from /lib64/libc.so.6

So it seems that rte_eth_rx_burst() calls  rte_eth_devices () and that
function crashes, presumably because of an illegal memory access.

Please can anyone suggest a way of debugging this further to determine the
cause?


More information about the users mailing list