DPDK usage discussions
 help / color / mirror / Atom feed
From: Harrish SJ <harrish@aviznetworks.com>
To: users@dpdk.org
Cc: IIanChezhian Raman <ilan.raman@aviznetworks.com>,
	Jatin Batra <confluence@aviznetworks.atlassian.net>
Subject: Reg the Valgrind support for DPDK App
Date: Wed, 1 May 2024 17:49:12 +0530	[thread overview]
Message-ID: <B0F19CD6-549E-4675-8E07-8444EF506398@aviznetworks.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 904 bytes --]

Hi DPDK Community,

We are trying to attach Valgrind to DPDK testpmd/helloworld APP but observing that the initialization is stuck for longer time in rte_eal_memory_init() —> rte_eal_memseg_init() —> memseg_primary_init() —> eal_dynmem_memseg_lists_init() —> eal_memseg_list_alloc() API with below logs:

==997317== Warning: set address range perms: large range [0x1405800000, 0x1805a00000) (noaccess)
==997317== Warning: set address range perms: large range [0x1405800000, 0x1805a00000) (noaccess)
==997317== Warning: set address range perms: large range [0x1405800000, 0x1805a00000) (noaccess)

We have tried with both standard Valgrind and https://github.com/bluca/valgrind-dpdk as well.
Could you please help us with the steps and procedure to run Valgrind for DPDK APP or any other procedures to find memleak in the code.?
Thanks in advance,

Regards and Thanks,
Harrish.S.J


[-- Attachment #2: Type: text/html, Size: 1453 bytes --]

                 reply	other threads:[~2024-05-01 12:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=B0F19CD6-549E-4675-8E07-8444EF506398@aviznetworks.com \
    --to=harrish@aviznetworks.com \
    --cc=confluence@aviznetworks.atlassian.net \
    --cc=ilan.raman@aviznetworks.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).