From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/27410] New: rpm-set path based probes
Date: Sat, 13 Feb 2021 00:00:29 +0000 [thread overview]
Message-ID: <bug-27410-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27410
Bug ID: 27410
Summary: rpm-set path based probes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
Bug #25568's introduced capabilities to specify probes by build-id, but this is
not very user friendly. What users tend to see directly are file names, and
occasionally filenames from archives that are not even installed.
The attachment is a demonstration prototype for a stap front-end that can take
a path name and a list of RPM-containing directories. It computes a
buildid-based script template based on finding all buildids for the given path
name in any of the RPMs found, and then compiles than via stap -p4. It uses a
temporary instance of debuginfod to build/serve the buildid executables /
debuginfo.
% sh stap-multirpm /usr/bin/vi /path/to/RPMs
[starts debuginfod -R /path/to/RPMs ...]
[chance to edit template SCRIPT.stp]
[compiles to stap_hexcode.ko]
[kills debuginfod]
% sudo staprun stap_hexcode.ko &
% /usr/bin/vi # of any version from any of those RPMs
[watch stap probe hit]
We should consider growing some native systemtap syntax for this. Suggestions
welcome. Possibility:
probe rpmsearch("/path/to/RPMs/prefix*").process("/path/name").function(...) {
}
probe debsearch(...) { }
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-02-13 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 0:00 fche at redhat dot com [this message]
2021-02-13 0:01 ` [Bug translator/27410] " fche at redhat dot com
2022-09-07 17:47 ` rgoldber at redhat dot com
2023-08-31 13:57 ` rgoldber 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-27410-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).