From: Stephen Hemminger <stephen@networkplumber.org>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Lalithaditya Naidu Gajula <lalithaditya96@gmail.com>,
users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Issue :- segmentation fault in rte_eal_wait_lcore.
Date: Wed, 22 Jan 2020 08:08:33 -0800 [thread overview]
Message-ID: <20200122080833.4cc3ed0f@hermes.lan> (raw)
In-Reply-To: <4cd99005-1777-0abd-caf9-ce2a46a5d45e@intel.com>
On Wed, 22 Jan 2020 10:52:28 +0000
"Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:
> On 20-Jan-20 7:34 AM, Lalithaditya Naidu Gajula wrote:
> > Hi All,
> > I got a segmentation fault issue regarding ret_eal_wait_lcore and
> > rte_eal_mp_wait_lcore(),
> > when i am running the code in a few logical cores using rte_eal_remote
> > _launch() function which has a while (1) (infinite loop) in all the
> > functions launched by remote launch and when i am terminating the code with
> > 'ctrl+c' i am getting segmentation fault at rte_eal_mp_wait_lcore(), then
> > I replaced that with rte_eal_wait_lcore() for the respective logical cores
> > even then i am getting a segmentation fault, can anyone please clarify this
> > issue?
> >
>
> It sounds like you have memory corruption somewhere in your code. Have
> you tried looking at it in gdb and stepping through your code to see if
> you get any wrong memory accesses?
>
It also possible to run DPDK code under valgrind. You do need the right
version of valgrind, and there can be some tuning issues.
prev parent reply other threads:[~2020-01-22 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 7:34 [dpdk-users] " Lalithaditya Naidu Gajula
2020-01-22 10:52 ` [dpdk-users] [dpdk-dev] " Burakov, Anatoly
2020-01-22 16:08 ` Stephen Hemminger [this message]
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=20200122080833.4cc3ed0f@hermes.lan \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=lalithaditya96@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).