Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi -

> [...] Or perhaps I'm jusy lazy. Basically... these two tools need a
> kernel "helper", need debugging symbol information (quite obviously,
> to print function args) [...]

Sorry about that, I'm spoiled with a distro that makes debuginfo
really easy to find & install. :-) I should have listed this variant
of the script instead.  It doesn't need debuginfo (because stap
developers have coded up a considerable heuristic database for
syscalls).

# stap -e '
probe nd_syscall.{adjtimex,clock_adjtime,clock_settime}
    { println(tid(), " ", ppfunc()," ",argstr) }
probe nd_syscall.{adjtimex,clock_adjtime,clock_settime}.return
    { println(tid(), " ", ppfunc()," ",retstr) }
'
25234 sys_adjtimex {ADJ_OFFSET|ADJ_MAXERROR|ADJ_ESTERROR|ADJ_STATUS|ADJ_TIMECONST, constant=3, esterror=16, freq=0, maxerror=16, offset=0, precision=0, status=1, tick=0, tolerance=0}
25234 sys_adjtimex 0 (TIME_OK)
[...]


- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Development]     [Linux USB Development]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux