From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28378] semantic error: process return probes not available [man error::inode-uprobes]
Date: Thu, 23 Sep 2021 12:31:10 +0000 [thread overview]
Message-ID: <bug-28378-6586-vMHckpZuhI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28378-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28378
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
Summary|[Systemtap] runtime error: |semantic error: process
|Kernel function symbol |return probes not available
|table missing [man |[man error::inode-uprobes]
|warning::symbols] |
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
The real issue isn't the warning, but the error:
semantic error: process return probes not available [man error::inode-uprobes]
Hopefully the information given is useful.
Try: man error::inode-uprobes
Which should give you:
https://manpages.ubuntu.com/manpages/impish/man7/error::inode-uprobes.7stap.html
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-09-23 12:31 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 ` mark at klomp dot org [this message]
2021-09-24 2:51 ` [Bug runtime/28378] semantic error: process return probes not available [man error::inode-uprobes] 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
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-vMHckpZuhI@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).