Re: Another Newbie question about measuring time in a sys call

[Li Guanglei <guanglei at cn dot ibm dot com>]

David A Sperry ??:
> I'm guessing the syscall tapsets may have changed and the associative array
> may be getting confused between a call and it's return (lseek vs
> lseek.return)

I greped in /usr/local/share/systemtap/tapsets/syscall.stp, and found 
 for the return of syscalls, in some places, it set name to 
syscallname, while in other places it set name to syscall.return, e.g.:

probe kernel.syscall.chdir.return =
   kernel.function("sys_chdir").return {
      name = "chdir.return"
}

probe syscall.accept.return = kernel.function("sys_accept").return {
  name = "accept"
  returnp = 1 /*seem to use returnp=1 to mark this as a return probe*/
}

so we need to make the name consistent.