From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27224] stap 4.4 'cannot attach to module' in debugfs mode as non-root
Date: Fri, 22 Jan 2021 04:31:12 +0000 [thread overview]
Message-ID: <bug-27224-6586-jPwvzzOX4K@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27224-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27224
--- Comment #2 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
Created attachment 13144
--> https://sourceware.org/bugzilla/attachment.cgi?id=13144&action=edit
stap -vvvv -DSTAP_TRANS_DEBUGFS output
Output from
$ sudo mount /sys/kernel/debug -o remount,mode=700
$ stap -vvvv -DSTAP_TRANS_DEBUGFS -e 'probe begin { printf("started\n");
exit(); }'
on stap 4.4 from systemtap-4.4-2.fc33.x86_64
I filtered it with
egrep -v '^(Skipping tapset|Processing)'
to reduce irrelevant spam.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-01-22 4:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 4:26 [Bug runtime/27224] New: " craig.ringer at 2ndquadrant dot com
2021-01-22 4:26 ` [Bug runtime/27224] " craig.ringer at 2ndquadrant dot com
2021-01-22 4:27 ` craig.ringer at 2ndquadrant dot com
2021-01-22 4:31 ` craig.ringer at 2ndquadrant dot com [this message]
2021-01-22 4:42 ` craig.ringer at 2ndquadrant dot com
2021-01-22 4:42 ` [Bug runtime/27224] stap 4.4 'cannot attach to module' in debugfs mode as non-root (WITH WORKAROUND) craig.ringer at 2ndquadrant dot com
2021-01-22 22:30 ` fche at redhat dot com
2021-01-22 22:31 ` fche at redhat dot com
2021-01-29 10:43 ` craig.ringer at 2ndquadrant 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-27224-6586-jPwvzzOX4K@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).