This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Where does systemtap look for debuginfo and sources ?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: "A, Satheeshpaul (EXT-Other - IN/Bangalore)" <satheeshpaul dot a dot ext at nsn dot com>
- Cc: <systemtap at sources dot redhat dot com>
- Date: Tue, 13 Apr 2010 11:21:22 -0400
- Subject: Re: Where does systemtap look for debuginfo and sources ?
- References: <9C3016725A35864D974EE3485093EDD101432BCF@SGSIEXC007.nsn-intra.net>
"A, Satheeshpaul (EXT-Other - IN/Bangalore)" <satheeshpaul.a.ext@nsn.com> writes:
> I am having trouble in probing a module that did not come with the RHEL
> 5.4 distribution.
Systemtap does work with this configuration but only clumsily.
> I have installed the kernel-debuginfo & kernel-devel
> packages. The kernel-debuginfo packages puts the debug-build modules
> under "/usr/lib/debug/lib/modules/2.6.18-164.el5/kernel/" . I have
> copied my module (built with -g and no optimisation) in this location. I
> also copied the sources of this module under
> "/usr/src/debug/kernel-2.6.18/linux-2.6.18.x86_64/net". But systemtap is
> still not able to find the probe point.
If your .ko is not stripped, then you should need do nothing but copy
it under /lib/modules/`uname -r`/kernel somewhere. stap should find
it, and its embedded dwarf data.
You don't need to install the module sources anywhere, nor do you need
to put something under /usr/lib/debug/lib/modules/.... unless it's a
stripped .ko.debug file.
- FChE