Messages in this thread | | | Date | Fri, 15 Sep 2006 11:18:47 -0700 | From | Martin Bligh <> | Subject | Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 |
| |
>>Also, care to explain how kprobes can be used to access same data >>without having to actually customize a probe point for every binary? > > > Thats why we have things like systemtap. > > All we appear to lack is systemtap ability to parse debug data so it can > be told "trace on line 9 of sched.c and record rq and next"
But that's the whole point - if it's not integrated into a marker as source code, it requires manual intervention for every bloody release to do. "line 9 of sched.c" is a farcically stupid way of doing tags on a dynamically moving project like the linux kernel.
Yes, that may work OK for something that is very static, like a distro snapshot, but as a general mechanism, it's unsustainable and broken.
M. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |