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]

[PATCH 0/5] Synchronize nd_syscalls.stp with syscalls.stp


Hi,

Here are a few patches for nd_syscalls.stp to sync it with syscalls.stp.

Fourth patch is problematic. From a theoretical viewpoint it isn't flawed.
Though applying it causes my strace-like script almost inoperative.
http://research.pawelczyk.it/systemtap/scripts/strace-nd.stp

Typical use case:
./strace-nd.stp -vc /bin/ls

It hangs after reporting many probe registration errors (rc -22), the last
one is kprobe.function("SyS_epoll_create").return!
After typing Ctrl-C script is stopped, but no data was collected and
process /bin/ls probably wasn't started -- there is no output from it.

Other scenario:
./strace-nd.stp -v

Now only fstat hits the probe.

Any ideas where is the source of problem?

Regards.

Przemyslaw Pawelczyk (5):
  Unify formatting of nd_syscalls.stp.
  Remove return probes for exit[_group] in nd_syscalls.stp.
  Add missing probe points in nd_syscalls.stp.
  Fix nd_syscalls.stp for architectures using SYSCALL_WRAPPERS.
  Uncomment 'name' variable in nd_syscall.lseek probe point.

 tapset/nd_syscalls.stp | 1207 ++++++++++++++++++++++++++++++++----------------
 1 files changed, 809 insertions(+), 398 deletions(-)


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