Hi Zhenyu,
If I understandd your question correctly, I can think of two ways to
trace an arbitrary kernel function. First, you can hook the tracer on
a dynamic probe[1] using something like this:
lttng enable-event customEventName -k --probe kernelFunctionName.
You can also hook the tracer on
On Mon, Feb 16, 2015 at 5:33 AM, Ranganadh Kanitmahanti
ranganadh1...@yahoo.com wrote:
hi,
We are using babeltrace 1.2.4 and LTTng Trace Control 2.5.3. Continously
giving babeltrace is throwing this error. Sorry about previous
conversation. I am actually getting this reading a snapshot
hi,We are using babeltrace 1.2.4 and LTTng Trace Control 2.5.3. Continously
giving babeltrace is throwing this error. Sorry about previous conversation. I
am actually getting this reading a snapshot session . I have given continously
babeltrace and path to read the traces . Then I am getting
Hi,
We are using BabelTrace Trace Viewer and Converter 1.2.4
Thanks Regards,K.V.Ranganadh.
On Friday, 13 February 2015 8:19 PM, Jérémie Galarneau
jeremie.galarn...@efficios.com wrote:
On Fri, Feb 13, 2015 at 12:47 AM, Ranganadh Kanitmahanti
ranganadh1...@yahoo.com wrote:
Hi,