This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Fw: ãnewãproblems when running the following script
- From: Mark Wielaard <mjw at redhat dot com>
- To: zshan <zshan at cse dot buaa dot edu dot cn>
- Cc: "fche at sourceware dot org" <fche at sourceware dot org>, systemtap <systemtap at sourceware dot org>
- Date: Mon, 25 May 2009 10:25:04 +0200
- Subject: Re: Fw: ãnewãproblems when running the following script
- References: <200905232314148393474@cse.buaa.edu.cn> <200905241941159686858@cse.buaa.edu.cn>
Hi zshan,
On Sun, 2009-05-24 at 19:41 +0800, zshan wrote:
________________________________________________________________________
> åääï zshan
> åéæéï 2009-05-23 23:14:14
> æääï Mark Wielaard; fche@redhat.com
> æéï systemtap
> äéï [new]problems when running the following script
>
> details are attached
>
> HTML document attachment (attachment.html)
Please do NOT attach HTML to your messages, they will NOT reach the
list. And then nobody else can see your messages and try to help you.
> plain text document attachment (attach.txt)
> [...]
> WARNING: cannot find module bridge debuginfo: No DWARF information
> found
> semantic error: no match while resolving probe point
> module("bridge").function("*")
> dwarf_builder releasing kernel dwflpp
> semantic error: no probes found
> Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0
> global(s) in 100usr/140sys/235real ms.
> Pass 2: analysis failed. Try again with another '--vp 01' option.
> Running rm -rf /tmp/staphKGpAd
>
>
> I really have no idea why?
I don't immediately see what is wrong here.
I do notice that my own bridge.ko.debug file is located under:
/usr/lib/debug/lib/modules/2.6.18-128.1.10.el5xen/kernel/net/bridge/bridge.ko.debug
And I don't have to copy anything around.
Please see if your systemtap and kernel installation are sane.
See http://sourceware.org/systemtap/wiki/HowToReportBugs
Please include all information listed there.
And please don't send HTML message since they won't be accepted to the
mailinglist.
Thanks,
Mark