From 2d9735b70fe3faf18e21e6e4c0ed20c3ca48b7fa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Th=C3=A9ophile=20Bastian?= Date: Thu, 2 Aug 2018 13:47:50 +0200 Subject: [PATCH] Talk about Libunwind --- report/report.tex | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/report/report.tex b/report/report.tex index d1dcbdb..3ba9f85 100644 --- a/report/report.tex +++ b/report/report.tex @@ -213,7 +213,12 @@ drastically the unwinding process. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \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}