From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/27975] could systemtap probe user process running in docker(overlay2 fs)?
Date: Mon, 14 Jun 2021 17:42:29 +0000 [thread overview]
Message-ID: <bug-27975-6586-zj7PoUQc77@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27975-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27975
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
Running a stap module built with super verbosity like
stap -DDEBUG_TASK_FINDER -DDEBUG_TASK_FINDER_VMA -DDEBUG_SYMBOLS
-DDEBUG_UPROBES [...]
may let you see the difference.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-06-14 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 7:44 [Bug uprobes/27975] New: " q1875486458 at gmail dot com
2021-06-10 14:45 ` [Bug uprobes/27975] " fche at redhat dot com
2021-06-10 16:59 ` q1875486458 at gmail dot com
2021-06-14 17:42 ` fche at redhat dot com [this message]
2021-10-08 3:15 ` 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-27975-6586-zj7PoUQc77@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).