From aa72cb6ab9b546143a9513b8d956bb47276c69d5 Mon Sep 17 00:00:00 2001 From: Bartosz Taudul Date: Fri, 14 Aug 2020 00:41:28 +0200 Subject: [PATCH] Update manual. --- manual/tracy.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/tracy.tex b/manual/tracy.tex index 9ae4fdfd..087dcebd 100644 --- a/manual/tracy.tex +++ b/manual/tracy.tex @@ -1353,7 +1353,7 @@ To have proper call stack information, the profiled application must be compiled \begin{itemize} \item On MSVC open the project properties and go to \emph{Linker\textrightarrow Debugging\textrightarrow Generate Debug Info}, where the \emph{Generate Debug Information} option should be selected. -\item On gcc or clang remember to specify the debugging information \texttt{-g} parameter during compilation and omit the strip symbols \texttt{-s} parameter. Link the executable with an additional option \texttt{-rdynamic} (or \texttt{-{}-export-dynamic}, if you are passing parameters directly to the linker). +\item On gcc or clang remember to specify the debugging information \texttt{-g} parameter during compilation and \emph{do not} add the strip symbols \texttt{-s} parameter. Additionally, omitting frame pointers will severely reduce the quality of stack traces, which can be fixed by adding the \texttt{-fno-omit-frame-pointer} parameter. Link the executable with an additional option \texttt{-rdynamic} (or \texttt{-{}-export-dynamic}, if you are passing parameters directly to the linker). \item On OSX you may need to run \texttt{dsymutil} to extract the debugging data out of the executable binary. \item On iOS you will have to add a \emph{New Run Script Phase} to your XCode project, which will execute the following shell script: