From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4671 invoked by alias); 26 May 2006 06:48:58 -0000 Received: (qmail 4663 invoked by uid 22791); 26 May 2006 06:48:58 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from e4.ny.us.ibm.com (HELO e4.ny.us.ibm.com) (32.97.182.144) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 May 2006 06:48:51 +0000 Received: from sd0109e.au.ibm.com (d23rh905.au.ibm.com [9.190.250.124]) by e4.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4Q6j2Te026278 for ; Fri, 26 May 2006 02:45:03 -0400 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.250.237]) by sd0109e.au.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4Q6mIv3088802 for ; Fri, 26 May 2006 16:48:22 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k4Q6iY6J026186 for ; Fri, 26 May 2006 16:44:34 +1000 Received: from [9.124.35.96] ([9.124.35.96]) by d23av04.au.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4Q6iXnA026020 for ; Fri, 26 May 2006 16:44:33 +1000 Message-ID: <4476A441.9080004@in.ibm.com> Date: Fri, 26 May 2006 06:48:00 -0000 From: Srinivasa D S Organization: IBM User-Agent: Thunderbird 1.5 (X11/20060313) MIME-Version: 1.0 To: systemtap@sources.redhat.com Subject: probing the "label" is not working correctly Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q2/txt/msg00500.txt.bz2 Hi I have installed systemtap on FC5 machine(i386 platform). I am able to write scripts and execute them. I found one problem when probing labels in kernel function. "copy_process" has "fork_out" label and I write script like below it works probe kernel.statement(0xc0118846).label("fork_out") { printf("iam here %s %d\n",execname(),pid()); } [root@localhost probedef]# cat /proc/kallsyms | grep c0118846 c0118846 t copy_process =================================================== but if I change the address in to "copy_process", I am getting this error probe kernel.statement("copy_process").label("fork_out") { printf("iam here %s %d\n",execname(),pid()); } [root@localhost probedef]# stap -vvvv label.stp Created temporary directory "/tmp/stapGHPUp4" Searched '/usr/local/share/systemtap/tapset/2.6.15-1.2054_FC5/i686/*.stp', match count 0 Searched '/usr/local/share/systemtap/tapset/2.6.15-1.2054_FC5/*.stp', match count 0 Searched '/usr/local/share/systemtap/tapset/2.6.15/i686/*.stp', match count 0 Searched '/usr/local/share/systemtap/tapset/2.6.15/*.stp', match count 0 Searched '/usr/local/share/systemtap/tapset/2.6/i686/*.stp', match count 0 Searched '/usr/local/share/systemtap/tapset/2.6/*.stp', match count 0 Searched '/usr/local/share/systemtap/tapset/i686/*.stp', match count 1 Searched '/usr/local/share/systemtap/tapset/*.stp', match count 16 Pass 1: parsed user script and 17 library script(s) in 100usr/0sys/138real ms. parsed 'copy_process' -> func 'copy_process' pattern 'kernel' matches module 'kernel' focused on module 'kernel' = [c0100000-c042f25c, bias 0] semantic error: incomplete: do not know how to interpret .label: identifier 'probe' at label.stp:6:2 pattern 'kernel' matches module 'kernel' semantic error: no match for probe point while: resolving probe point kernel.statement("copy_process").label("fork_out") Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 global(s) in 190usr/30sys/243real ms. Pass 2: analysis failed. Try again with more '-v' (verbose) options. Running rm -rf /tmp/stapGHPUp4 ============================================================== Shouldn't we use function name while probing label? Please comment Thanks Srinivasa DS