From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-20024-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 682 invoked by alias); 11 Oct 2012 19:22:01 -0000
Received: (qmail 621 invoked by uid 48); 11 Oct 2012 19:21:41 -0000
From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/14706] New: Support multiple target processes in stapdyn
Date: Thu, 11 Oct 2012 19:22:00 -0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: dyninst
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jistone at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-14706-6586@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
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: 2012-q4/txt/msg00060.txt.bz2


http://sourceware.org/bugzilla/show_bug.cgi?id=14706

             Bug #: 14706
           Summary: Support multiple target processes in stapdyn
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: dyninst
        AssignedTo: systemtap@sourceware.org
        ReportedBy: jistone@redhat.com
    Classification: Unclassified


We should support multiple target processes in stapdyn.  This primarily means
following fork/exec process children from the initial target, but it could also
mean allowing multiple -c/-x targets, if we want.

We'll need shared memory between targets, at least for global variables
(including per-thread stats memory, so anyone can aggregate).  Any events that
are not process specific (e.g. begin, end, timers) can run in the stapdyn
process, like they are now for the case with no target process.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.