patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: "Singh, Aman Deep" <aman.deep.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [RFC 3/3] app/testpmd: fix hex string parser in flow commands
Date: Wed, 29 Sep 2021 13:30:00 +0000	[thread overview]
Message-ID: <DM6PR12MB37530E76AB22DB349ADB01A9DFA99@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB1367BA7923A136D5109AD7C4A3A99@CY4PR11MB1367.namprd11.prod.outlook.com>

Hi, Aman

An example:

testpmd> flow create 0 ingress pattern eth / end actions rss key 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef queues 0 end / end

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5de366d in __memset_sse2 () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install elfutils-libelf-0.170-4.el7.x86_64 glibc-2.17-222.el7.x86_64 jansson-2.10-1.el7.x86_64 libnl3-3.2.28-4.el7.x86_64 numactl-libs-2.0.9-7.el7.x86_64 openssl-libs-1.0.2k-12.el7.x86_64 zlib-1.2.7-17.el7.x86_64
(gdb)

With best regards,
Slava

From: Singh, Aman Deep <aman.deep.singh@intel.com>
Sent: Wednesday, September 29, 2021 15:23
To: Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: dev@dpdk.org; Ori Kam <orika@nvidia.com>; stable@dpdk.org
Subject: Re: [dpdk-dev] [RFC 3/3] app/testpmd: fix hex string parser in flow commands

Hi Ovsiienko,

Can you please provide the flow command which causes "segmentation fault".

Thanks
Aman

      reply	other threads:[~2021-09-29 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 12:22 Singh, Aman Deep
2021-09-29 13:30 ` Slava Ovsiienko [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=DM6PR12MB37530E76AB22DB349ADB01A9DFA99@DM6PR12MB3753.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=stable@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).