zhangengru/tracy
1
0
Fork 0
mirror of https://github.com/wolfpld/tracy.git synced 2025-03-20 07:40:02 +08:00
Code Issues Projects Wiki Activity

move the symbol resolving functionality to the update application instead of creating a new one

Browse Source
This commit is contained in:
Tiago Rodrigues
2023-11-24 20:48:39 -05:00
parent a1ca8dd06a
commit de6e7d2fc3
16 changed files with 90 additions and 876 deletions
Download Patch File Download Diff File Expand all files Collapse all files
manual/tracy.tex
+4 -4
View File
@@ -1792,12 +1792,12 @@ As an alternative to to runtime symbol resolution, we can set the environment va
the minimal set of info required for offline resolution (a shared library path and an offset into that shared library).
The generated tracy capture will have callstack frames symbols showing \texttt{[unresolved]}.
The \texttt{tracy-edit} tool can be used to load that capture, perform symbol resolution offline
The \texttt{update} tool can be used to load that capture, perform symbol resolution offline
(by passing \texttt{-r}) and writing out a new capture with symbols resolved.
By default \texttt{tracy-edit} will use the original shared libraries paths that were recorded
By default \texttt{update} will use the original shared libraries paths that were recorded
in the capture (which assumes running in the same machine or a machine with identical
filesystem setup as the one used to run the tracy instrumented application).
You can do path substitution with the \texttt{-s} option to perform any number of path
You can do path substitution with the \texttt{-p} option to perform any number of path
substitions in order to use symbols located elsewhere.
\begin{bclogo}[
@@ -1805,7 +1805,7 @@ noborder=true,
couleur=black!5,
logo=\bcbombe
]{Important}
Beware that \texttt{tracy-edit} will use any matching symbol file to the path it resolved to (no symbol version checking is done), so if the symbol file doesn't match the code that was used when doing the callstack capturing you will get incorrect results.
Beware that \texttt{update} will use any matching symbol file to the path it resolved to (no symbol version checking is done), so if the symbol file doesn't match the code that was used when doing the callstack capturing you will get incorrect results.
\end{bclogo}
\subsection{Lua support}