From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29993 invoked by alias); 15 Feb 2006 16:34:43 -0000 Received: (qmail 29954 invoked by uid 22791); 15 Feb 2006 16:34:41 -0000 X-Spam-Status: No, hits=-2.5 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.31) with ESMTP; Wed, 15 Feb 2006 16:34:39 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k1FGYb9O018477 for ; Wed, 15 Feb 2006 11:34:37 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k1FGYW106058; Wed, 15 Feb 2006 11:34:32 -0500 Received: from [172.16.59.162] (dhcp59-162.rdu.redhat.com [172.16.59.162]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id k1FGYWFb023048; Wed, 15 Feb 2006 11:34:32 -0500 Message-ID: <43F35817.4020004@redhat.com> Date: Wed, 15 Feb 2006 16:34:00 -0000 From: William Cohen User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nathan DeBardeleben CC: "systemtap@sources.redhat.com" Subject: Re: Inserting a probe point into a module? References: <43F352F5.10303@lanl.gov> In-Reply-To: <43F352F5.10303@lanl.gov> 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-q1/txt/msg00527.txt.bz2 Nathan DeBardeleben wrote: > I'm sure this has been asked before but I didn't see it looking around. > Can I use systemtap / kprobes to probe a point that's in a module that's > been isnmodded? Something I really need to do is probe points in an > InfiniBand driver. I have the network driver module source, so I know > where I want to probe... but just not sure if it's possible. > > My instinct is that it might not be possible because we don't have the > appropriate kernel-debuginfo for this module... or can I create it somehow? > > Thanks! > You can probe modules installed in the kernel. You need to used "probe module("mod").function("func"). Assuming that the module has been built with debugging information this should work. The debuginfo rpm is needed for the normal kernel because the debug information isn't included in the normal vmlinuz and is stripped out of the modules during the normal RPM build process. If you are building the module locally, it should still have that information in the module. -Will