From 4848bf113103d72de9267e71f9a56723d69b7a8b Mon Sep 17 00:00:00 2001
From: Kurt Kanzenbach <kurt@linutronix.de>
Date: Tue, 5 Mar 2019 11:58:10 +0100
Subject: 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>
---
 .../debugging-tools/pres_debugging-tools_en.tex        | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

(limited to 'application-devel/debugging-tools/pres_debugging-tools_en.tex')

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
-- 
cgit v1.2.3

