[bootlin/training-materials updates] master: Stop mentioning DUMA, not updated since 2009 (c5d3af97)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/c5d3af973666a324d1b7008af129b0a9a9e62bca

>---------------------------------------------------------------

commit c5d3af973666a324d1b7008af129b0a9a9e62bca
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Tue Jun 2 07:48:41 2020 +0200

    Stop mentioning DUMA, not updated since 2009
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

c5d3af973666a324d1b7008af129b0a9a9e62bca
 .../sysdev-application-development.tex               | 20 +-------------------
 1 file changed, 1 insertion(+), 19 deletions(-)

diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index 426fbfb4..2ceefe9e 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -408,7 +408,7 @@
     \code{gdbserver /dev/ttyS0 <executable> <args>}
   \item Otherwise, attach \code{gdbserver} to an already running program:\\
     \code{gdbserver --attach localhost:<port> <pid>}
-  \item Then, on the host, start \code{ARCH-linux-gdb program},\\
+  \item Then, on the host, start \code{ARCH-linux-gdb <executable>},\\
     and use the following \code{gdb} commands:
     \begin{itemize}
     \item To connect to the target:\\
@@ -446,24 +446,6 @@
 
 \subsection{Memory checkers}
 
-\begin{frame}
-  \frametitle{DUMA}
-  Detect Unintended Memory Access\\
-  \url{http://duma.sourceforge.net/}
-  \begin{itemize}
-  \item Fork and replacement for Electric Fence
-  \item Stops your program on the exact instruction that overruns or
-    underruns a \code{malloc()} memory buffer.
-  \item GDB will then display the source-code line that causes the
-    bug.
-  \item Works by using the virtual-memory hardware to create a
-    red-zone at the border of each buffer - touch that, and your
-    program stops.
-  \item Works on any platform supported by Linux, whatever the CPU
-    (provided virtual memory support is available).
-  \end{itemize}
-\end{frame}
-
 \begin{frame}
   \frametitle{Valgrind (1)}
   \begin{columns}[T]