From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/31180] New: Feature request: new probe process.data(ADDR).* probe-points
Date: Mon, 18 Dec 2023 20:08:07 +0000 [thread overview]
Message-ID: <bug-31180-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31180
Bug ID: 31180
Summary: Feature request: new probe process.data(ADDR).*
probe-points
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
Now that we have kernel.data(*).* probepoints for kernel-space hardware
breakpoints (or watchpoints) in stap, it is good to also have the userland hw
watchpoint support targeting a process.
The basic kernel facility is already there. The implementation should be quite
straight-forward, especially after the implementation of the existing
kernel.data(*) probes is just refactored.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-12-18 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 20:08 agentzh at gmail dot com [this message]
2023-12-18 20:48 ` [Bug translator/31180] " agentzh at gmail 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-31180-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).