From: "lijunlong at openresty dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/29986] New: kernel.function can not work on fedora34 with aarch64 architecture
Date: Wed, 11 Jan 2023 08:44:02 +0000 [thread overview]
Message-ID: <bug-29986-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29986
Bug ID: 29986
Summary: kernel.function can not work on fedora34 with aarch64
architecture
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: lijunlong at openresty dot com
Target Milestone: ---
OS: 5.11.12-300.fc34.aarch64
stap verion: Systemtap translator/driver (version 4.9/0.186,
release-4.8-15-gdf41f00d). (built from the source code)
Use stap -l to list the kernel functions, it will throw errors like below.
stap -vv -l 'kernel.function("vfs_*")'
Systemtap translator/driver (version 4.9/0.186, release-4.8-15-gdf41f00d)
Copyright (C) 2005-2022 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 6.1.0-rc3
enabled features: LIBXML2 NLS
Created temporary directory "/tmp/staptw6f30"
Session arch: arm64 release: 5.11.12-300.fc34.aarch64
Build tree: "/lib/modules/5.11.12-300.fc34.aarch64/build"
Searched for library macro files:
"/usr/local/openresty-stap/share/systemtap/tapset/linux", found: 7, processed:
7
Searched for library macro files:
"/usr/local/openresty-stap/share/systemtap/tapset", found: 11, processed: 11
Searched: "/usr/local/openresty-stap/share/systemtap/tapset/linux/arm64",
found: 2, processed: 2
Searched: "/usr/local/openresty-stap/share/systemtap/tapset/linux", found: 413,
processed: 413
Searched: "/usr/local/openresty-stap/share/systemtap/tapset/arm64", found: 1,
processed: 1
Searched: "/usr/local/openresty-stap/share/systemtap/tapset", found: 40,
processed: 40
Pass 1: parsed user script and 474 library scripts using
119052virt/104412res/9336shr/94904data kb, in 100usr/30sys/149real ms.
derive-probes (location #0): kernel.function("vfs_*") of keyword at <input>:1:1
semantic error: resolution failed in DWARF builder
thrown from: elaborate.cxx:1094
semantic error: resolution failed in DWARF builder
thrown from: elaborate.cxx:1094
semantic error: while resolving probe point: identifier 'kernel' at <input>:1:7
thrown from: elaborate.cxx:1082
source: probe kernel.function("vfs_*") {}
^
semantic error: no match
thrown from: elaborate.cxx:1045
Pass 2: analyzed script: 0 probes, 0 functions, 0 embeds, 0 globals using
121052virt/107052res/9948shr/96904data kb, in 150usr/10sys/149real ms.
Running rm -rf /tmp/staptw6f30
Spawn waitpid result (0x0): 0
Removed temporary directory "/tmp/staptw6f30"
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-01-11 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:44 lijunlong at openresty dot com [this message]
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
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@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).