From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6311 invoked by alias); 15 May 2007 22:02:07 -0000 Received: (qmail 6301 invoked by uid 22791); 15 May 2007 22:02:06 -0000 X-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,NO_REAL_NAME X-Spam-Check-By: sourceware.org Received: from njord.oit.pdx.edu (HELO njord.oit.pdx.edu) (131.252.120.57) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 May 2007 22:02:03 +0000 Received: from nithog.oit.pdx.edu (nithog.oit.pdx.edu [131.252.122.32]) by njord.oit.pdx.edu (8.13.3+/8.13.1) with ESMTP id l4FM1wnU018920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 May 2007 15:01:58 -0700 Received: from nithog.oit.pdx.edu (localhost.localdomain [127.0.0.1]) by nithog.oit.pdx.edu (8.13.3+/8.13.1) with ESMTP id l4FM1wQD001944; Tue, 15 May 2007 15:01:58 -0700 X-Authentication-Warning: nithog.oit.pdx.edu: Host localhost.localdomain [127.0.0.1] claimed to be nithog.oit.pdx.edu Received: (from sec@localhost) by nithog.oit.pdx.edu (8.13.3+/8.13.1) id l4FM1vLS001939; Tue, 15 May 2007 15:01:57 -0700 Received: from bi01p1.co.us.ibm.com (bi01p1.co.us.ibm.com [32.97.110.142]) by webmail.pdx.edu (Horde MIME library) with HTTP; Tue, 15 May 2007 15:01:57 -0700 Message-ID: <20070515150157.w22l7uob853k8k4w@webmail.pdx.edu> Date: Tue, 15 May 2007 22:02:00 -0000 From: patm@pdx.edu To: systemtap@sources.redhat.com Cc: David Smith Subject: Re: Listing probe alias resolution failures References: <20070515141427.d90m5pfzj4w0owok@webmail.pdx.edu> <464A2714.6040108@redhat.com> In-Reply-To: <464A2714.6040108@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.3) 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: 2007-q2/txt/msg00294.txt.bz2 Quoting David Smith : > patm@pdx.edu wrote: >> With (version 0.5.14 built 2007-04-30) of systemtap and kernel=20=20=20 >> 2.6.19.7 (i386), there are a lot (~220) of failures in the tapset=20=20= =20 >> like the following: >> >> semantic error: no match for probe point while resolving probe=20=20=20 >> point vm.write_shared_copy >> >> To get a list of all of these, I pulled out some code from the=20=20=20 >> systemtap GUI and made a quick standalone java program=20=20=20 >> "listprobes", it works like the following: > > I'm not a java programmer, but it appears like you might be expecting > every function listed in the tapsets to be resolvable on a particular > kernel. This isn't the case. Let's take an easy example - the probe > alias syscall.open (in tapset/syscalls2.stp): > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > probe syscall.open =3D > kernel.function("sys_open") ?, > kernel.function("compat_sys_open") ?, > kernel.function("sys32_open") ? > { > ... > } > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The java program lists all of the probe aliases, not their=20=20 corresponding kernel funtion(s). So all of the failures listed are for=20=20 the probe alias, which must happen as you described above, after=20=20 exhausting all listed kernel.functions and modules mapped to in the=20=20 probe definition. > This probe alias looks for "sys_open" first, then if it doesn't exist > looks for "compat_sys_open", then looks for "sys32_open". If > "sys_open" exists in your kernel, it isn't an error that > "compat_sys_open" and "sys32_open" do not exist. > > In actual use, if you've gotten "no match for probe point" errors let > us know and we'll try to fix them. > > --=20 > David Smith > dsmith@redhat.com > Red Hat > http://www.redhat.com > 256.217.0141 (direct) > 256.837.0057 (fax)