From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16366 invoked by alias); 18 May 2009 04:34:13 -0000 Received: (qmail 16358 invoked by uid 22791); 18 May 2009 04:34:12 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 May 2009 04:34:04 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n4I4XdsB032288; Mon, 18 May 2009 00:33:39 -0400 Received: from fche.csb (vpn-10-90.bos.redhat.com [10.16.10.90]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n4I4Xdip026248; Mon, 18 May 2009 00:33:39 -0400 Received: by fche.csb (Postfix, from userid 2569) id A495D58480; Mon, 18 May 2009 00:33:38 -0400 (EDT) Date: Mon, 18 May 2009 04:34:00 -0000 From: "Frank Ch. Eigler" To: zshan Cc: systemtap Subject: Re: Re: Re: Fw: Re: problem when running the following script Message-ID: <20090518043338.GB17190@redhat.com> References: <20090517180158.GA17190@redhat.com> <200905180923257051704@cse.buaa.edu.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905180923257051704@cse.buaa.edu.cn> User-Agent: Mutt/1.4.2.2i 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: 2009-q2/txt/msg00604.txt.bz2 Hi - On Mon, May 18, 2009 at 09:23:26AM +0800, zshan wrote: > > Well, maybe the TUN driver is not compiled into your kernel at all. > > Maybe it's somehow lumped into another module. (There is likely no > > "tun-debuginfo" package.) > I run the script and it shows that: > semantic error: no match while resolving probe point module("*").function("tun*") > [root@localhost ~]# stap -l 'kernel.function("tun*")' > semantic error: no match while resolving probe point kernel.function("tun*") grep TUN in your kernel .config file; grep tun_ in /proc/kallsyms. If empty, you don't have tun built, so pick another driver/module. Check that you have the correct version debuginfo for your kernel. Try the debuginfo-free kprobes.function("FOOBAR") variant. - FChE