From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12132 invoked by alias); 28 Oct 2008 16:00:55 -0000 Received: (qmail 12125 invoked by uid 22791); 28 Oct 2008 16:00:54 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,KAM_MX,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 28 Oct 2008 16:00:19 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m9SG0IEH009952; Tue, 28 Oct 2008 12:00:18 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m9SG0HWq001993; Tue, 28 Oct 2008 12:00:17 -0400 Received: from localhost.localdomain (dhcp-164.hsv.redhat.com [172.16.17.164]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m9SG0D7t029506; Tue, 28 Oct 2008 12:00:15 -0400 Message-ID: <4907370A.1020703@redhat.com> Date: Tue, 28 Oct 2008 16:00:00 -0000 From: David Smith User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: dcnltc@us.ibm.com CC: systemtap@sourceware.org Subject: Re: [PATCH] itrace spin lock fix References: <48FFC1D4.7000801@us.ibm.com> <4901F5E4.7030200@redhat.com> <49026917.7010808@us.ibm.com> <4905C3E9.1020401@redhat.com> <490731FC.6030702@us.ibm.com> In-Reply-To: <490731FC.6030702@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.27.26 X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q4/txt/msg00222.txt.bz2 Dave Nomura wrote: > Sorry, I forgot about that. The probe used to fire because Frank had > to disable the test because it was crashing. I'm not sure what has > changed that is preventing the itrace probe from firing. I experimented > a bit and found that if I added a uprobe that didn't do anything related > to the itrace probe, then the itrace probe would fire. This is going to > take further study. Any ideas on what might have changed? I'm afraid you question is a bit too broad for me to answer. As far as the task_finder goes, some internals have changed to support the new version of utrace, but the external interface hasn't changed. -- David Smith dsmith@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)