\pagestyle{empty} %
\thispagestyle{empty}

%% Attention: pas plus d'un recto-verso!
% Ne conservez pas les questions

\subsection*{The general context}

The standard debugging data format for ELF binary files, DWARF, contains a lot
of information. Among those are the stack unwinding data, which allows to
unwind stack frames, restoring machine registers to their proper values, for
instance within the context of a debugger.

As debugging data can easily get heavy beyond reasonable if stored carelessly,
the DWARF standard pays a great attention to data compactness and compression.
This, as always, is at the expense of efficiency: accessing stack unwinding
data for a particular program point can be quite costly.

The most widely used library used for stack unwinding,
\texttt{libunwind}~\cite{libunwind}, 

\subsection*{The research problem}

This internship explored the possibility to compile the standard ELF debugging
information format, DWARF, into x86\_64 assembly. 


\qtodo{Delete question} \textit{
What is the question that you studied?
Why is it important, what are the applications/consequences?
Is it a new problem?
If so, why are you the first researcher in the universe who consider it?
If not, why did you think that you could bring an original contribution?
}

\subsection*{Your contribution}

What is your solution to the question described in the last paragraph?

Be careful, do \emph{not} give technical details, only rough ideas!

Pay a special attention to the description  of the \emph{scientific} approach.

\subsection*{Arguments supporting its validity}

What is the evidence that your solution is a good solution?
Experiments? Proofs?

Comment the robustness of your solution: how does it rely/depend on the working assumptions?

\subsection*{Summary and future work}

What is next? In which respect is your approach general?
What did your contribution bring to the area?
What should be done now?
What is the good \emph{next} question?

\pagestyle{plain}
