Talk about Libunwind
This commit is contained in:
parent
36de838a89
commit
2d9735b70f
1 changed files with 6 additions and 1 deletions
|
@ -213,7 +213,12 @@ drastically the unwinding process.
|
||||||
|
|
||||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
\subsection{Unwinding state-of-the-art}
|
\subsection{Unwinding state-of-the-art}
|
||||||
\todo{}
|
|
||||||
|
The most commonly used library to perform stack unwinding, in the Linux
|
||||||
|
ecosystem, is \prog{libunwind}~\cite{libunwind}. While it is very robust and
|
||||||
|
quite efficient, most of its optimization comes from fine-tuned code and good
|
||||||
|
caching mechanisms. While parsing DWARF, \prog{libunwind} is forced to parse
|
||||||
|
the relevant FDE from its start, until it finds the row it was seeking.
|
||||||
|
|
||||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
\subsection{General statistics}
|
\subsection{General statistics}
|
||||||
|
|
Loading…
Reference in a new issue