[bootlin/training-materials updates] master: Embedded Linux: debugger improvements (9d7c0ef4)

[Michael Opdenacker]

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

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

commit 9d7c0ef41dd2aacfa8b2f5c51fa65071eb29bcb1
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Aug 3 14:52:44 2020 +0200

    Embedded Linux: debugger improvements
    
    - Fix text overflow issue
    - Mention command shortcuts
    - Remove ddd, 11 years without a release
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

9d7c0ef41dd2aacfa8b2f5c51fa65071eb29bcb1
 .../sysdev-application-development.tex             | 34 ++++++++++++----------
 1 file changed, 19 insertions(+), 15 deletions(-)

diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index 062e3e2a..4acbdf82 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -319,34 +319,38 @@
 \end{frame}
 
 \begin{frame}
-  \frametitle{GDB crash course}
+  \frametitle{GDB crash course (1)}
+  \small
   A few useful GDB commands
   \begin{itemize}
   \item \code{break foobar}\\
-    puts a breakpoint at the entry of function \code{foobar()}
+    Put a breakpoint at the entry of function \code{foobar()}
   \item \code{break foobar.c:42}\\
-    puts a breakpoint in \code{foobar.c}, line 42
+    Put a breakpoint in \code{foobar.c}, line 42
   \item \code{print var} or \code{print task->files[0].fd}\\
-    prints the variable \code{var}, or a more complicated reference. GDB
+    Print the variable \code{var}, or a more complicated reference. GDB
     can also nicely display structures with all their members
-  \item \code{continue}\\
-    continue the execution
-  \item \code{next}\\
-    continue to the next line, stepping over function calls
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
+  \frametitle{GDB crash course (2)}
+  \small
+  \begin{itemize}
+  \item \code{continue} (\code{c})\\
+    Continue the execution after a breakpoint
+  \item \code{next} (\code{n})\\
+    Continue to the next line, stepping over function calls
   \item \code{step}\\
-    continue to the next line, entering into subfunctions
-  \item \code{backtrace}\\
-    display the program stack
+    Continue to the next line, entering into subfunctions
+  \item \code{backtrace} (\code{bt})\\
+    Display the program stack
   \end{itemize}
 \end{frame}
 
 \begin{frame}
   \frametitle{GDB graphical front-ends}
   \begin{itemize}
-  \item {\bf DDD} - Data Display Debugger\\
-    \url{https://www.gnu.org/software/ddd/}\\
-    A popular graphical front-end, with advanced data plotting
-    capabilities.
   \item {\bf GDB/Insight}\\
     \url{https://sourceware.org/insight/}\\
     From the GDB maintainers.