From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/5236] process memory map tracker
Date: Wed, 31 Oct 2007 21:05:00 -0000 [thread overview]
Message-ID: <20071031210535.11971.qmail@sourceware.org> (raw)
In-Reply-To: <20071031203811.5236.fche@redhat.com>
------- Additional Comments From jkenisto at us dot ibm dot com 2007-10-31 21:05 -------
Roland's utrace TODO list (http://people.redhat.com/roland/utrace/TODO) includes
a "mmap change event," which would presumably call a client callback when a VM
area is created/removed/resized/moved. If you could create an initial map
(possibly in a sleepy context) and then catch map changes as they happen, you
could have an up-to-date version available even in can't-sleep contexts.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5236
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-10-31 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 20:38 [Bug runtime/5236] New: " fche at redhat dot com
2007-10-31 21:05 ` jkenisto at us dot ibm dot com [this message]
2008-04-30 21:13 ` [Bug runtime/5236] " 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=20071031210535.11971.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).