From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25568] New: buildid-based process probes
Date: Mon, 17 Feb 2020 20:49:00 -0000 [thread overview]
Message-ID: <bug-25568-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25568
Bug ID: 25568
Summary: buildid-based process 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: ---
It may be desirable to let a stap script identify userspace process probes not
by path name but by buildid:
probe process("hexcode").function/statement(...) { } // as usual
... or some explicit functor for 'buildid' addressing.
The semantics would be:
probe all processes systemwide whereever given elf binary is mapped
This would allow a single stap script to operate against a multitude of
-versions- of a userspace binary. It could also let it operate with binaries
loaded from non-default locations, such as container-mapped filesystem mount
points.
Working with elfutils/debuginfod, systemtap should load binaries & debuginfo by
buildid just fine.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-02-17 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 20:49 fche at redhat dot com [this message]
2020-02-19 21:10 ` [Bug translator/25568] " fche at redhat dot com
2020-02-26 17:03 ` amerey at redhat dot com
2020-03-03 20:31 ` amerey 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-25568-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).