From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-2427-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 12403 invoked by alias); 8 Feb 2006 01:52:14 -0000
Received: (qmail 12396 invoked by uid 22791); 8 Feb 2006 01:52:13 -0000
X-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_00,DNS_FROM_RFC_ABUSE,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from ausmtp04.au.ibm.com (HELO ausmtp04.au.ibm.com) (202.81.18.152)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 08 Feb 2006 01:52:12 +0000
Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) 	by ausmtp04.au.ibm.com (8.12.10/8.12.10) with ESMTP id k181wOF2117250 	for <systemtap@sources.redhat.com>; Wed, 8 Feb 2006 12:58:24 +1100
Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.250.244]) 	by sd0208e0.au.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k181tKVU244384 	for <systemtap@sources.redhat.com>; Wed, 8 Feb 2006 12:55:20 +1100
Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) 	by d23av03.au.ibm.com (8.12.11/8.13.3) with ESMTP id k181q5J5007030 	for <systemtap@sources.redhat.com>; Wed, 8 Feb 2006 12:52:05 +1100
Received: from [127.0.0.1] ([9.181.131.208]) 	by d23av03.au.ibm.com (8.12.11/8.12.11) with ESMTP id k181ptwB006828; 	Wed, 8 Feb 2006 12:52:03 +1100
Message-ID: <43E94EB8.5000906@cn.ibm.com>
Date: Wed, 08 Feb 2006 01:52:00 -0000
From: Li Guanglei <guanglei@cn.ibm.com>
Organization: IBM CSTL
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: David A Sperry <David_A_Sperry@raytheon.com>
CC: systemtap@sources.redhat.com
Subject: Re: Another Newbie question about measuring time in a sys call
References: <OF9A980AD4.6A1AABB6-ON8525710F.0006CB90-8525710F.000827AB@mck.us.ray.com>
In-Reply-To: <OF9A980AD4.6A1AABB6-ON8525710F.0006CB90-8525710F.000827AB@mck.us.ray.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
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: 2006-q1/txt/msg00421.txt.bz2

David A Sperry ??:
> 
> 
> I'm guessing the syscall tapsets may have changed and the associative array
> may be getting confused between a call and it's return (lseek vs
> lseek.return)
> 

I greped in /usr/local/share/systemtap/tapsets/syscall.stp, and found 
  for the return of syscalls, in some places, it set name to 
syscallname, while in other places it set name to syscall.return, e.g.:

probe kernel.syscall.chdir.return =
    kernel.function("sys_chdir").return {
       name = "chdir.return"
}

probe syscall.accept.return = kernel.function("sys_accept").return {
   name = "accept"
   returnp = 1 /*seem to use returnp=1 to mark this as a return probe*/
}

so we need to make the name consistent.