Skip to contentSkip to conversation

ktap: Another dynamic tracing tool for Linux

RFC Michel Dagenais 1 participant 1 message Jan 14, 2013 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 68461756.264831358192004350.JavaMail.root@srv11.zimbra.polymtl.ca

#1 lore raw
Quoted 10 lines · ----- "Jovi Zhang
Quoted 2 lines · Michel Dagenais

You may be interested in KGTP which implements a simple bytecode interpreter in the kernel to accept GDB tracepoints

http://code.google.com/p/kgtp/

Quoted 2 lines

The bytecode is quite limited but would be easy to extend.

KGTP is still not meet my requirement on Linux tracing. ktap don't have gcc or gdb dependence, it's build from scratch, with a clean design, this is very important.

KGTP uses the GDB remote protocol but does not use/require GDB. If you have the needed information about symbols, offsets... you can generate and send the bytecode yourself.

Quoted 5 lines
Quoted 3 lines

Eventually we should be able to connect LTTng http://lttng.org/ and KGTP in order to benefit from the efficiency of LTTng for activating probes and retrieving data.

You are right, LTTng should be possible, and I already planed it, also on some functionality of ftrace and systemtap.

Such dynamic capabilities are definitely of interest both in kernel and userspace tracing.