<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 03/14/2014 01:50 PM, Mathieu
Desnoyers wrote:<br>
</div>
<blockquote
cite="mid:138917049.3594.1394830210179.JavaMail.zimbra@efficios.com"
type="cite">
<pre wrap="">Hi everyone,
I pushed a new features in LTTng-UST that I'm sure everyone will like.
USAGE WITH TRACEF
The simplest way to add instrumentation to your code is by far the
tracef() API. To you it, in a nutshell:
1) #include <lttng/tracef.h>
2) /* in your code, use like a printf */
tracef("my message, this integer %d", 1234);
3) Link your program against liblttng-ust.so.
4) Enable the UST event "lttng_ust_tracef:event" when tracing with the
following sequence of commands from lttng-tools:
lttng create; lttng enable-event -u "lttng_ust_tracef:event"; lttng start
[... run your program ...]
lttng stop; lttng view
That's it!
If you want to have more flexibility and control on the event names,
payload typing, etc, you can continue reading on and use the trace‐
points below. "tracef()" is there for quick and dirty ad hoc instrumen‐
tation, whereas tracepoint.h is meant for thorough instrumentation of a
code base to be integrated with an upstream project.
Feedback is welcome!
</pre>
</blockquote>
<br>
I haven't seen vocal support for this yet, so let me just say this
is a *very* welcome addition. Today, one of the first questions we
get from our customers is "how do I create new tracepoints in my
code?", and unfortunately that's almost always a very painful
discussion. Having this API available would be a big help.<br>
<br>
<div class="moz-signature">Hollis Blanchard<br>
Product Owner, <a href="http://go.mentor.com/codebench">Sourcery
CodeBench</a> and <a
href="http://go.mentor.com/sourceryanalyzer">Sourcery Analyzer</a><br>
Mentor Graphics Embedded Software Division<br>
</div>
<br>
</body>
</html>