From: Stephen Hemminger <stephen@networkplumber.org>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] DPDK Memory in GDB
Date: Tue, 3 Oct 2017 08:49:19 -0700 [thread overview]
Message-ID: <20171003084919.5ee9a3a7@xeon-e3> (raw)
In-Reply-To: <DA060131-0A97-457B-915B-0535721577EF@cloudsimple.com>
On Tue, 3 Oct 2017 15:11:32 +0530
Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
> Hi All,
>
> We have been using the mempool of the DPDK for our application. Whenever there is a core dump and if I try to print the contents of the pointer allocated from rte_malloc gdb is throwing an error saying cannot access the memory at address. During run time this is working fine . This happens only when examining a core. I replaced rte_mallloc with malloc and in this case I am able to print the contents of the pointer. I have built DPDK with -g option. Am I doing anything wrong here?
>
> Thanking You,
> Param.
That is probably intentional. Core dumps don't dump huge page memory (to save space). A 16G core file would not work well.
Also hugepages are shared between multiple processes.
prev parent reply other threads:[~2017-10-03 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 9:41 Kumaraparameshwaran Rathnavel
2017-10-03 15:49 ` 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=20171003084919.5ee9a3a7@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=krath@cloudsimple.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).