From 312b7190f841a26a9b2fd66914d18698c54ed26f Mon Sep 17 00:00:00 2001 From: Bartosz Taudul Date: Sat, 26 Oct 2019 16:59:54 +0200 Subject: [PATCH] Mention that only release builds should be profiled. --- manual/tracy.tex | 2 ++ 1 file changed, 2 insertions(+) diff --git a/manual/tracy.tex b/manual/tracy.tex index bb8869c2..20c91087 100644 --- a/manual/tracy.tex +++ b/manual/tracy.tex @@ -322,6 +322,8 @@ If that's not an option, copy all files from the Tracy checkout directory to you In the default configuration Tracy is disabled. This way you don't have to worry that the production builds will perform collection of profiling data. You will probably want to create a separate build configuration, with the \texttt{TRACY\_ENABLE} define, which enables profiling. +The application you want to profile should be compiled with all the usual optimization options enabled (i.e.~make a release build). It makes no sense to profile debugging builds, as the unoptimized code and additional checks (asserts, etc.) completely change how the program behaves. + Finally, on Unix make sure that the application is linked with libraries \texttt{libpthread} and \texttt{libdl}. \subsubsection{Short-lived applications}