public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "barrdetwix at gmail 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 01:42:48 +0000	[thread overview]
Message-ID: <bug-16836-6586-O3ZC0eVaWk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16836-6586@http.sourceware.org/bugzilla/>

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

--- Comment #4 from barrdetwix at gmail dot com ---
Here's 200kB of log with -DDEBUG_UNWIND=2 leading up to the "DWARF expression
stack underflow in CFI": https://paste.mozilla.org/VewSs2i7#L8,258,3146

(Note that there's a couple non-stap lines in the long becase I'm not running
stap directly, my reproducer is a small tool that starts a target process
suspended, generates a stap script for that process, and captures stap output.
And so far the CFI underflow problem reproduces perfectly only when I run my
tool under itself.)

Happy to upload vmlinux or some other binary if that would help any.

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

  parent reply	other threads:[~2020-10-06  1:42 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
2020-10-06  1:42 ` barrdetwix at gmail dot com [this message]
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-O3ZC0eVaWk@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).