This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

What is needed to run systemtap on a module built out of tree?


Hi... 

	We are trying to put probes on a module for RHEL4.5 that is
	built out of try (qlogic driver).  We get errors like: 

ïstap scsiinq.stp
WARNING: cannot find module qla2xxx debuginfo: invalid section index
WARNING: cannot find module qla2xxx debuginfo: invalid section index
semantic error: no match for probe point while resolving probe point
module("qla2xxx").function("qla2x00_issue_scsi_inquiry")
Pass 2: analysis failed. Try again with more '-v' (verbose) options

	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. 

	How do we deal with this situation?   We can control the
	build of the module, so we added CONFIG_DEBUG_INFO and
	CONFIG_KPROBES, but it still fails in the same way. 

	Thanks,

	Rick 
-- 
+----------------------------------------------------------------------+
| Rick Beldin                    |  Hewlett-Packard Company            |
| email: Rick.Beldin@hp.com      |  Global Solutions Engineering       |
| WTEC Linux, RHCE               |  5555 Windward Parkway West         |
|                                |  Alpharetta, GA 30004               |
+----------------------------------------------------------------------+


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]