From: Lewis Donzis <lew@perftech.com>
To: dev <dev@dpdk.org>
Subject: Including contigmem in core dumps
Date: Mon, 27 May 2024 19:34:44 -0500 (CDT) [thread overview]
Message-ID: <1771016800.166016.1716856484319.JavaMail.zimbra@donzis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
I've been wondering why we exclude memory allocated by eal_get_virtual_area() from core dumps? (More specifically, it calls eal_mem_set_dump() to call madvise() to disable core dumps from the allocated region.)
On many occasions, when debugging after a crash, it would have been very convenient to be able to see the contents of an mbuf or other object allocated in contigmem space. And we often avoid using the rte memory allocator just because of this.
Is there any reason for this, or could it perhaps be a compile-time configuration option not to call madvise()?
[-- Attachment #2: Type: text/html, Size: 771 bytes --]
next reply other threads:[~2024-05-28 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 0:34 Lewis Donzis [this message]
2024-05-28 6:55 ` Dmitry Kozlyuk
2024-05-28 13:19 ` Lewis Donzis
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=1771016800.166016.1716856484319.JavaMail.zimbra@donzis.com \
--to=lew@perftech.com \
--cc=dev@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).