This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: What is needed to run systemtap on a module built out of tree?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: rick dot beldin at hp dot com
- Cc: "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>
- Date: Thu, 05 Jun 2008 16:01:56 -0400
- Subject: Re: What is needed to run systemtap on a module built out of tree?
- References: <1212693407.7563.72.camel@evonc6220.americas.hpqcorp.net>
Rick Beldin <rick.beldin@hp.com> writes:
> [...]
> The structure of the module is that it is a 3rd party
> replacement module that is built out of tree from the
> rest of RHEL. It doesn't use rpmbuild and doesn't get
> delivered in an rpm. As a result, we don't have a
> debuginfo, or rather we have the RH debuginfo for the
> module of the SAME name but a DIFFERENT module.
> [...]
Can you zap somehow the RH qla2xxx .ko and .ko.debug files? Can you
ensure that your build of the .ko includes all the .debug_* sections?
- FChE