From: "nylon7717 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28378] semantic error: process return probes not available [man error::inode-uprobes]
Date: Fri, 24 Sep 2021 08:25:50 +0000 [thread overview]
Message-ID: <bug-28378-6586-14VSk6m706@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28378-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28378
--- Comment #5 from Nylon Chen <nylon7717 at gmail dot com> ---
Hi Mark Wielaard,
thanks for your help
When I use process.statement() or process.function replace
process.function().return
I can fix "error::inode-uprobes" issue
but my stap has other error
"semantic error: while processing probe tp_syscall.read.return from:
nd_syscall.read.return from: syscall.read.return from: syscall.read.return"
I try to reduce this stap script
```
...
probe syscall.write { write_fds[tid()] = fd }
probe syscall.write.return {
p = pid()
// Get fd even if non-dwarf syscall return probe.
fd = write_fds[tid()]
delete write_fds[tid()]
bytes = retval
time = gettimeofday_us() - @entry(gettimeofday_us())
if (bytes > 0)
filewrite[p, fd] <<< bytes
time_io[p, fd] <<< time
}
...
```
the error message point out the problem is "syscall.xxx.return"
I try to comment (/**/) it, and the compiler's result is ok
I just curious about this result.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-09-24 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 9:29 [Bug runtime/28378] New: [Systemtap] runtime error: Kernel function symbol table missing [man warning::symbols] nylon7717 at gmail dot com
2021-09-23 12:31 ` [Bug runtime/28378] semantic error: process return probes not available [man error::inode-uprobes] mark at klomp dot org
2021-09-24 2:51 ` nylon7717 at gmail dot com
2021-09-24 5:50 ` nylon7717 at gmail dot com
2021-09-24 8:06 ` mark at klomp dot org
2021-09-24 8:25 ` nylon7717 at gmail dot com [this message]
2021-09-24 8:46 ` mark at klomp dot org
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-28378-6586-14VSk6m706@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).