From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/26660] New: probe kernel.statement(HEX).absolute incorrectly requires kernel debuginfo
Date: Thu, 24 Sep 2020 02:37:14 +0000 [thread overview]
Message-ID: <bug-26660-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26660
Bug ID: 26660
Summary: probe kernel.statement(HEX).absolute incorrectly
requires kernel debuginfo
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
To use stap to translate the following stap script:
```
probe kernel.statement(0xffffffff881075a0).absolute {
println("Hit")
exit()
}
```
we got the following error when kernel debuginfo is not present in the current
system:
```
semantic error: while resolving probe point: identifier 'kernel' at a.stp:1:7
source: probe kernel.statement(0xffffffff881075a0).absolute {
^
semantic error: while resolving probe point: identifier 'kernel' at :1:7
source: probe kernel.statement(0xffffffff881075a0).absolute {
^
semantic error: missing x86_64 kernel/module debuginfo [man warning::debuginfo]
under '/lib/modules/5.0.16-100.fc28.x86_64/build'
Pass 2: analysis failed. [man error::pass2]
```
But actually this probe point does not need kernel debug symbols at all.
I'll prepare a patch to fix it.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-09-24 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 2:37 agentzh at gmail dot com [this message]
2020-09-24 4:27 ` [Bug translator/26660] " agentzh at gmail 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-26660-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).