Closed Apitronix closed 4 years ago
This is the problem with putting examples in the README which reference internal kernel functions, sometimes they change :sweat_smile:
You'll have to look in /proc/kallsyms
to find out what the corresponding functions are called now. I quick look on my own system (also 5.3.x) indicates that syscall are now prefixed with __x64_sys_
. So, for example, to trace all syscalls you can run a script like this:
ply 'k:__x64_sys_!(perf_event_open) { @[caller] = count(); }'
perf_event_open
is not allowed to be traced, so it must be excluded.
I'll leave this issue open until I've had time to put better examples in the README.
Thank you for reporting this.
Arf... You're right ! :-) Thanks !
Hi there !
I have a problem with
ply
. When I try to execute some of your README examples, I have an error code returned :I think this problem is similar to the issue #7 , but I'm not sure. So I tried the Brendan's solution:
Some additional information about the system: