From: fche@redhat.com (Frank Ch. Eigler)
To: Cong Wu <congwu@alauda.io>
Cc: "systemtap\@sourceware.org" <systemtap@sourceware.org>
Subject: Re: a idea about probe proc path like /proc/pid/root/xxx
Date: Thu, 18 Aug 2022 13:35:37 -0400 [thread overview]
Message-ID: <87wnb5mp3c.fsf@redhat.com> (raw)
In-Reply-To: <HK0PR01MB34916D6B6B1BD921A62CCA64C9899@HK0PR01MB3491.apcprd01.prod.exchangelabs.com>
Cong Wu <congwu@alauda.io> writes:
> hi all. currently, I'm use stap to probe user process like `probe
> process("/proc/xx/root/xxx").function("a")`, what I really want is to
> probe a process running in docker, I make a small patch.
Interesting idea.
> [...]
> basically if solib_pathname start with /proc/$(task->tgid)/root then i
> just compare the rest part of it.
That's an interesting solution. Does it work fully? Have you tried the
buildid-based probing facility, which is independent of run-time paths
such as containers/namespace? We're also working on another extension
that is related: https://sourceware.org/bugzilla/show_bug.cgi?id=27410
- FChE
prev parent reply other threads:[~2022-08-18 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 5:18 Cong Wu
2022-08-18 17:35 ` Frank Ch. Eigler [this message]
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=87wnb5mp3c.fsf@redhat.com \
--to=fche@redhat.com \
--cc=congwu@alauda.io \
--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).