public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* stap examples build
@ 2008-01-04  9:47 manjunath k
  2008-01-04 15:11 ` David Smith
  0 siblings, 1 reply; 2+ messages in thread
From: manjunath k @ 2008-01-04  9:47 UTC (permalink / raw)
  To: systemtap

Hi,

 Im trying to build the systemtap example in the following way
"stap -k -p4 -vv examples/iotime.stp" and got the below errors.
Is this the way to build the examples, what is the cause and
how can we rectify this error.


Error seen
--------------

Created temporary directory "/tmp/stappEgbzr"
Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 1
Searched '/usr/local/share/systemtap/tapset/*.stp', found 36
Pass 1: parsed user script and 37 library script(s) in 400usr/20sys/423real ms.
semantic error: libdwfl failure (missing kernel debuginfo): No such
file or directory while resolving probe point
kernel.function("sys_open")?
semantic error: no match for probe point while resolving probe point
syscall.open
semantic error: no match for probe point while resolving probe point
syscall.open.return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_read")
semantic error: no match for probe point while resolving probe point
syscall.read
semantic error: no match for probe point while resolving probe point
kernel.function("sys_read").return
semantic error: no match for probe point while resolving probe point
syscall.read.return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_write")
semantic error: no match for probe point while resolving probe point
syscall.write
semantic error: no match for probe point while resolving probe point
kernel.function("sys_write").return
semantic error: no match for probe point while resolving probe point
syscall.write.return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_close")
semantic error: no match for probe point while resolving probe point
syscall.close
Pass 2: analyzed script: 1 probe(s), 34 function(s), 1 embed(s), 8
global(s) in 10usr/0sys/15real ms.
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
Keeping temporary directory "/tmp/stappEgbzr"

-Manju

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: stap examples build
  2008-01-04  9:47 stap examples build manjunath k
@ 2008-01-04 15:11 ` David Smith
  0 siblings, 0 replies; 2+ messages in thread
From: David Smith @ 2008-01-04 15:11 UTC (permalink / raw)
  To: manjunath k; +Cc: systemtap

manjunath k wrote:
> Hi,
> 
>  Im trying to build the systemtap example in the following way
> "stap -k -p4 -vv examples/iotime.stp" and got the below errors.
> Is this the way to build the examples, what is the cause and
> how can we rectify this error.
> 
> 
> Error seen
> --------------
> 
> Created temporary directory "/tmp/stappEgbzr"
> Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 1
> Searched '/usr/local/share/systemtap/tapset/*.stp', found 36
> Pass 1: parsed user script and 37 library script(s) in 400usr/20sys/423real ms.
> semantic error: libdwfl failure (missing kernel debuginfo): No such
> file or directory while resolving probe point

The first error seen here is the problem - you either don't have the
kernel debuginfo installed or systemtap can't find it.

If you are on a fedora based system, you'll need kernel-debuginfo,
kernel-debuginfo-common, and kernel-devel installed to use systemtap.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-01-04 15:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-04  9:47 stap examples build manjunath k
2008-01-04 15:11 ` David Smith

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).