public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/16836] CFI expression underflow occurs during unwinding on some kernels
Date: Tue, 06 Oct 2020 00:18:01 +0000	[thread overview]
Message-ID: <bug-16836-6586-OOOtTMaUSa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16836-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16836

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fche at redhat dot com

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
I believe stack -underflow- can only occur if the DWARF CFI data is invalid, or
if we interpret it in an incorrect manner.  It'd really help to extract that
somehow.  Or try running with  

    stap -DDEBUG_UNWIND=2 [...]

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2020-10-06  0:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11 21:48 [Bug runtime/16836] New: " lberk at redhat dot com
2014-04-11 21:48 ` [Bug runtime/16836] " lberk at redhat dot com
2014-04-14 15:54 ` tromey at redhat dot com
2014-04-14 20:09 ` lberk at redhat dot com
2017-10-11 10:44 ` mark at klomp dot org
2017-10-11 10:48 ` mjw at fedoraproject dot org
2020-10-05 23:15 ` barrdetwix at gmail dot com
2020-10-06  0:18 ` fche at redhat dot com [this message]
2020-10-06  1:42 ` barrdetwix at gmail dot com
2020-10-06 12:04 ` mark at klomp dot org

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-16836-6586-OOOtTMaUSa@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).