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]

Re: socket-trace.stp: no match while resolving probe point kernel.function("*@net/socket.c")


On Wed, 2008-10-29 at 21:41 -0400, Dongtao Liu wrote:
> Thank you for reply. I found it pretty strange that if I do not use
> "*@net/socket.c" but use function in socket.c directly such as
> sock_create. SystemTap can work well and trace all the calls of
> fuction sock_create. I don't know why...

That is indeed strange. So this works for you:
$ stap -e 'probe kernel.function("sock_sendmsg"){log(pp())}'
But this doesn't:
$ stap -e 'probe kernel.function("sock_sendmsg@net/socket.c"){log(pp())}'

Does the output (pp()) of the running version, or if you run it with
-vv, give any hints about the why?

Cheers,

Mark


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