From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-15435-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 10482 invoked by alias); 12 Mar 2010 18:13:45 -0000
Received: (qmail 10436 invoked by uid 48); 12 Mar 2010 18:13:34 -0000
Date: Fri, 12 Mar 2010 18:13:00 -0000
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20100312181334.11373.fche@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug testsuite/11373] New: systemtap.server/server.exp leaves stap_*.ko litter
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: 2010-q1/txt/msg00646.txt.bz2

server.exp uses [stap_run_batch] to run stap-client
via the $net_path hack.  For each successful test, a
stap_NNNN.ko file is left behind in the testsuite build
directory.

If these buildok tests are the only place that uses
net_path, we should consider unhacking that, and
writing a special [stap_run_batch] proc variant that
knows it's being used for stap-client purposes.  It
can then clean up stap_NNNN.ko residue.

-- 
           Summary: systemtap.server/server.exp leaves stap_*.ko litter
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.