From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/13714] panic when sampling backtrace() in timer.profile
Date: Mon, 20 Feb 2012 22:08:00 -0000 [thread overview]
Message-ID: <bug-13714-6586-mltQPqZaDJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13714-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13714
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|systemtap at sourceware dot |mjw at redhat dot com
|org |
--- Comment #2 from Mark Wielaard <mjw at redhat dot com> 2012-02-20 22:08:21 UTC ---
Found the root cause of this issue. It happens when a DW_CFA operation that
defines the CFA as dwarf expression is followed by a DW_CFA operation that
(re)defined the CFA as register+offset. In that case we forgot the reset the
REG_STATE.cfa_is_expr flag which made compute_expr() interpret the reg/offset
as expr pointer (because they share their values in a union).
While adding more sanity checks to make sure we catch such issues I found what
looks like bad CFI in the x86_64 kernel in common_interrupt
(arch/x86/kernel/entry_64.S) which defines CFI "by hand" and has a
CFI_DEF_CFA_REGISTER following a def_cfa_expression, which is invalid.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2012-02-20 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 6:29 [Bug runtime/13714] New: " brendan.gregg at joyent dot com
2012-02-20 14:30 ` [Bug runtime/13714] " mjw at redhat dot com
2012-02-20 22:08 ` mjw at redhat dot com [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=bug-13714-6586-mltQPqZaDJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).