From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/29986] kernel.function can not work on fedora34 with aarch64 architecture
Date: Wed, 11 Jan 2023 15:20:44 +0000 [thread overview]
Message-ID: <bug-29986-6586-k2CHufJJd4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29986-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29986
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wcohen at redhat dot com
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
The kernel.function("*") probes are going to need the kernel-debuginfo* rpms.
What is the output of:
rpm -qa |grep kernel-
Are there kernel-debuginfo and kernel-debuginfo-common that match the
kernel-5.11.12-300.fc34.aarch64 that is currently running?
I set up a fc34 machine locally and found that the kernels that were installed
were kernel-5.17.12-100.fc34.aarch64, a later version that used in this bug.
Most of the rpm repos remove the older versions of the debuginfo for pacage and
you may need to download the matching kernel-debuginfo-* rpms directly from
koji rather than using the stap-prep command as stap-prep won't find the
appropriate kernel-debuginfo* rpms.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-01-11 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:44 [Bug translator/29986] New: " lijunlong at openresty dot com
2023-01-11 15:20 ` wcohen at redhat dot com [this message]
2023-01-11 16:00 ` [Bug translator/29986] " fche at redhat dot com
2023-01-11 17:04 ` wcohen at redhat dot com
2023-01-12 1:53 ` lijunlong at openresty dot com
2023-01-12 1:54 ` lijunlong at openresty dot com
2023-01-12 19:42 ` wcohen at redhat dot com
2023-06-08 11:02 ` wcohen at redhat dot com
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-29986-6586-k2CHufJJd4@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).