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]

Newb: Probe My Application


Hello,

I recently found out about systemtap and am still getting the hang of
things. I'm interested in trying to use systemtap as an alternative to a
debugger to probe my own program that I wrote. To test things out I
wrote a simple program and comiled it to an executable. But after this
I'm stumped as to what to do to get systemtap to find the probe points
in my program.

So let's say I have an executable "foo" compiled with g++ using the -g
flag. How do I tell systemtap that I'm interested in all methods within
that one executable? All the examples I've seen so far point towards
kernel related probes. Is this something that can be done using
systemtap?

I've tried:

probe module("foo").*

probe process("./foo").*

And run the scripts using the following command:

> stap foo.stp -c foo

The first didn't find any probe points the second gave me a compilation
error on "pass 4". Any advice to a helpless newb?

Thanks!
Hassan


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