Bug 5236 - process memory map tracker
Summary: process memory map tracker
Status: RESOLVED DUPLICATE of bug 5951
Alias: None
Product: systemtap
Classification: Unclassified
Component: runtime (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Reported: 2007-10-31 20:38 UTC by Frank Ch. Eigler
Modified: 2008-04-30 20:52 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Frank Ch. Eigler 2007-10-31 20:38:11 UTC
we need a widget either in the systemtap runtime proper, or within
staprun/stapio, to tell a probe the memory layout of a given user process.  This
is basically the contents of /proc/$$/maps, and is necessary in order to place
kprobes, relocate unwind/symbol data, and probably other stuff too.  Some of it
needs to be available by probe initialization (uprobe placement) time.  It needs
to be kept reasonably up to date, and readable without taking sleepy locks (for
backtrace purposes).
Comment 1 Jim Keniston 2007-10-31 21:05:33 UTC
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.
Comment 2 Frank Ch. Eigler 2008-04-30 20:52:28 UTC

*** This bug has been marked as a duplicate of 5951 ***