From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/20541] Systemtap 3.0 installation problem on Ubuntu 16.04 LTS @GCP
Date: Wed, 31 Aug 2016 13:47:00 -0000 [thread overview]
Message-ID: <bug-20541-6586-g8uJcTZHxQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20541-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20541
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Your build appears fine, but:
> Pass 5: starting run.
> WARNING: probe
> kernel.function("SyS_open@/build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.
> 4.0/fs/open.c:1038") (address 0x
> ffffffff811fcd40) registration error (rc -84)
This error is coming from the kernel, as it rejects our proposed probe.
Does
# sudo grep -i sys.open /proc/kallsyms
give a matching address (...811fcd40) on your machine? If so, stap probably
isn't doing anything wrong, and we'll have to work around kernel limitations.
One possibility is to use
# stap -P ...
(prologue-searching to offset probe PC). Another is to smoke-test stap against
other probe points
# stap -e 'probe nd_syscall.* { }' -c 'sleep 10'
to see whether many other functions are affected by this registration error,
only only this one.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-08-31 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 7:54 [Bug server/20541] New: " steve.tsai at nexusguard dot com
2016-08-31 13:47 ` fche at redhat dot com [this message]
2016-09-01 2:59 ` [Bug server/20541] " steve.tsai at nexusguard dot com
2017-05-09 15:36 ` fche at redhat dot com
2024-02-21 15:43 ` fche 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-20541-6586-g8uJcTZHxQ@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).