From: Stephen Hemminger <stephen@networkplumber.org>
To: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: rte_eth_dev_stop crashing consistently
Date: Mon, 17 Feb 2025 07:58:19 -0800 [thread overview]
Message-ID: <20250217075819.5d9af8df@hermes.local> (raw)
In-Reply-To: <CACh--sg11BumMrNS-uap95JT9+G8H4L5QOOrgy2X0k02gBnY5A@mail.gmail.com>
On Mon, 17 Feb 2025 18:36:07 +0530
Lokesh Chakka <lvenkatakumarchakka@gmail.com> wrote:
> Hello,
>
> I've written a few pieces of code for sending and receiving packets.
> Here is the link for the same.
>
> If I try running only pmd_tx.c or only pmd_rx.c, I'm not seeing any crashes.
> But if the same code is copied into dpdk_tx_rx.c, I'm seeing a consistent
> crash.
>
> Can someone help me understand what I'm doing wrong?
>
>
> Thanks & Regards
> --
> Lokesh Chakka.
This is all your own code, so it is up to you to debug it.
Did you try running in debugger (gdb) and/or enabling some of the debug
flags in the DPDK build. The debug flags will cause more of the code paths
to validate arguments.
next prev parent reply other threads:[~2025-02-17 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:06 Lokesh Chakka
2025-02-17 15:58 ` Stephen Hemminger [this message]
2025-02-18 4:18 ` Lokesh Chakka
2025-02-19 13:39 ` Lokesh Chakka
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=20250217075819.5d9af8df@hermes.local \
--to=stephen@networkplumber.org \
--cc=lvenkatakumarchakka@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).