From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 929] rte_dump_stack() is not safe to call from signal handler
Date: Thu, 27 Jan 2022 20:47:39 +0000 [thread overview]
Message-ID: <bug-929-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=929
Bug ID: 929
Summary: rte_dump_stack() is not safe to call from signal
handler
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
A common scenario is to have a signal handler call rte_dump_stack().
Unfortunately, existing version is not safe in signal handler because it
assumes that malloc pool is not corrupted.
https://www.gnu.org/software/libc/manual/html_node/Backtraces.html
Better alternative is libunwind or libbacktrace
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-01-27 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 20:47 bugzilla [this message]
2022-06-24 8:26 ` bugzilla
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=bug-929-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).