diff options
| author | Kurt Kanzenbach <kurt@linutronix.de> | 2019-03-05 11:58:10 +0100 |
|---|---|---|
| committer | John Ogness <john.ogness@linutronix.de> | 2019-03-06 12:36:36 +0106 |
| commit | 4848bf113103d72de9267e71f9a56723d69b7a8b (patch) | |
| tree | 2df69a05e7df1c083cf3dbb4060dd12cd1846abf | |
| parent | 1c18bd7b0c9d56d6bf6a60418fb62fd3e0cb3699 (diff) | |
app/debugging: add description slide for address sanitizer
Add a brief introduction about what the address sanitizer actually is and what
types of bugs in can find. That's useful for our customers.
Requested-by: Holger Dengler <holger.dengler@linutronix.de>
Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
| -rw-r--r-- | application-devel/debugging-tools/pres_debugging-tools_en.tex | 18 |
1 files changed, 17 insertions, 1 deletions
diff --git a/application-devel/debugging-tools/pres_debugging-tools_en.tex b/application-devel/debugging-tools/pres_debugging-tools_en.tex index ed34c3b..5c5b552 100644 --- a/application-devel/debugging-tools/pres_debugging-tools_en.tex +++ b/application-devel/debugging-tools/pres_debugging-tools_en.tex @@ -615,7 +615,23 @@ $ valgrind --leak-check=full ./array_access \end{verbatim} \end{frame} -\begin{frame}[fragile]{AddressSanitizer} +\begin{frame}{AddressSanitizer} + \begin{block}{About AddressSanitizer} + \begin{itemize} + \item Fast memory error detector + \item Based on compiler instrumentation and shadow memory + \item Available for \textbf{gcc} and \textbf{clang} + \end{itemize} + \end{block} + \begin{block}{Types of bugs} + \begin{itemize} + \item Buffer overflows (heap, stack, global) + \item Use-after-free, dangling pointers, ... + \end{itemize} + \end{block} +\end{frame} + +\begin{frame}[fragile]{AddressSanitizer Example} \begin{verbatim} $ gcc -o array_access -fsanitize=address array_access.c $ ./array_access |