public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 08 Jun 2023 11:02:54 +0000	[thread overview]
Message-ID: <bug-29986-6586-mdf24HHkfP@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
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #7 from William Cohen <wcohen at redhat dot com> ---
This appears to be a missing or missmatched kernel-debugfino rpm.  On aarch64
Fedora 38 this worked for me with both the offical systemtap-4.8-3.fc38.aarch64
and a locally built systemtap from git commit
fc6519089d3f9366470ce442b648d69ed9b56f53.

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

      parent reply	other threads:[~2023-06-08 11:02 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 ` [Bug translator/29986] " wcohen at redhat dot com
2023-01-11 16:00 ` 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 [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-29986-6586-mdf24HHkfP@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).