From 066f96acd2ed844c60e32aa2037e6270ca82821e Mon Sep 17 00:00:00 2001 From: =?utf8?q?S=C3=A9bastien=20Boisvert?= Date: Sun, 19 Oct 2014 13:22:30 -0500 Subject: [PATCH] tracing-your-own-user-application: add details MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Sébastien Boisvert --- contents/getting-started/tracing-your-own-user-application.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contents/getting-started/tracing-your-own-user-application.md b/contents/getting-started/tracing-your-own-user-application.md index f899e7d..18e3258 100644 --- a/contents/getting-started/tracing-your-own-user-application.md +++ b/contents/getting-started/tracing-your-own-user-application.md @@ -18,9 +18,9 @@ Unlike `printf()`, though, `tracepoint()` does not use a format string to know the types of its arguments: the formats of all tracepoints must be defined before using them. So before even writing our _Hello world_ program, we need to define the format of our tracepoint. This is done by writing a -**template file**, with a name usually ending with the `.tp` extension, +**template file**, with a name usually ending with the `.tp` extension (for **t**race**p**oint), which the `lttng-gen-tp` tool (shipped with LTTng-UST) will use to generate -an object file and a header to be included in our application source code. +an object file (along with a `.c` file) and a header to be included in our application source code. Here's the whole flow: -- 2.34.1