From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24639] "next" statement not recognized by stap bpf backend
Date: Thu, 06 Jun 2019 21:37:00 -0000 [thread overview]
Message-ID: <bug-24639-6586-SPiZmuGWEq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24639-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24639
--- Comment #5 from Serhei Makarov <me at serhei dot io> ---
Weird, since it passes consistently on earlier 4.18.0 kernel. To me that trace
looks like something went wrong writing to the global variable map.
Which kernel version are you using on Fedora 30?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-06-06 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:29 [Bug bpf/24639] New: " wcohen at redhat dot com
2019-06-05 20:34 ` [Bug bpf/24639] " me at serhei dot io
2019-06-06 21:13 ` wcohen at redhat dot com
2019-06-06 21:30 ` wcohen at redhat dot com
2019-06-06 21:30 ` wcohen at redhat dot com
2019-06-06 21:37 ` me at serhei dot io [this message]
2019-06-07 13:49 ` wcohen at redhat dot com
2019-06-10 17:11 ` me at serhei dot io
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-24639-6586-SPiZmuGWEq@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).