DPDK usage discussions
 help / color / mirror / Atom feed
From: David Aldrich <david.aldrich.ntml@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Segmentation fault in rte_eth_devices()
Date: Wed, 10 Jun 2020 17:28:07 +0100	[thread overview]
Message-ID: <CAJK_iehCe7W1mfg=3uM3si=hhAke=iEOWtZDAnzOYHUGxgLXtA@mail.gmail.com> (raw)

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@entry=0
'\000', uiMaxNumOfRxFrm=uiMaxNumOfRxFrm@entry=7,
    pISocketListener=pISocketListener@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?

             reply	other threads:[~2020-06-10 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 16:28 David Aldrich [this message]
2020-06-11  8:57 ` David Aldrich
2020-06-12  0:55   ` Vincent Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJK_iehCe7W1mfg=3uM3si=hhAke=iEOWtZDAnzOYHUGxgLXtA@mail.gmail.com' \
    --to=david.aldrich.ntml@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).