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: Rick Beldin <rick dot beldin at hp dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>
- Date: Thu, 05 Jun 2008 20:22:14 +0000
- Subject: Re: What is needed to run systemtap on a module built out of tree?
- Organization: WTEC Linux
- References: <1212693407.7563.72.camel@evonc6220.americas.hpqcorp.net> <y0my75jk5vv.fsf@ton.toronto.redhat.com>
- Reply-to: rick dot beldin at hp dot com
On Thu, 2008-06-05 at 20:01 +0000, Frank Ch. Eigler wrote:
> 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?
>
Minutes after asking the question, we found that replacing
the RH-supplied debuginfo was causing the problem. After
building the module with CONFIG_DEBUG_INFO and CONFIG_KPROBE
and REPLACING the debuginfo from RH, it worked. I'm not
convinced that CONFIG_KPROBE was necessary.
Thanks for the quick response...
R
--
+----------------------------------------------------------------------+
| Rick Beldin | Hewlett-Packard Company |
| email: Rick.Beldin@hp.com | Global Solutions Engineering |
| WTEC Linux, RHCE | 5555 Windward Parkway West |
| | Alpharetta, GA 30004 |
+----------------------------------------------------------------------+