This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Pointing systemtap to an out of tree kernel module
- From: David Smith <dsmith at redhat dot com>
- To: Elie De Brauwer <eliedebrauwer at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Tue, 03 Jul 2012 16:15:27 -0500
- Subject: Re: Pointing systemtap to an out of tree kernel module
- References: <4FF34B33.9020405@gmail.com>
On 07/03/2012 02:42 PM, Elie De Brauwer wrote:
> Hello list,
>
> I'm doing a little experiment with systemtap, where I'm trying to do
> remote cross-system-tapping. Meaning on my laptop I have a
> cross-compiler, my kernel and and module in some path which isn't
> related to the kernel directory. And I'd like to create a script which
> allows me to gather information on the custom module. But I don't see
> any way to specify to systemtap where it should look for my kernel
> module (and debug symbols).
>
> And I'm just trying to glue something to probe
> module("common").function("*"). Now suppose my module lives in
> /home/e/module how would I tell systemtap that that might be an
> interesting place to look for it ?
Read stappaths man page, and look for the "Debuginfo Path" section.
Basically set SYSTEMTAP_DEBUGINFO_PATH.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)