From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-7609-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 28435 invoked by alias); 31 Oct 2007 20:38:21 -0000
Received: (qmail 28388 invoked by uid 48); 31 Oct 2007 20:38:11 -0000
Date: Wed, 31 Oct 2007 20:38:00 -0000
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20071031203811.5236.fche@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug runtime/5236] New: process memory map tracker
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2007-q4/txt/msg00271.txt.bz2

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).

-- 
           Summary: process memory map tracker
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


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.