[bootlin/training-materials updates] master: Debugging / tracing slides: minor improvements (82919556)

[Michael Opdenacker]

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

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

commit 82919556c9f99f649e5292f0a6586df7402d9d14
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Mar 1 15:13:14 2021 +0100

    Debugging / tracing slides: minor improvements
    
    - Add more gdb abbreviated commands
    - Mention that ltrace works better with glibc
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

82919556c9f99f649e5292f0a6586df7402d9d14
 .../sysdev-application-development.tex                     | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index c88835a3..ab761fe5 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -334,11 +334,11 @@
   \small
   A few useful GDB commands
   \begin{itemize}
-  \item \code{break foobar}\\
+  \item \code{break foobar} (\code{b})\\
     Put a breakpoint at the entry of function \code{foobar()}
   \item \code{break foobar.c:42}\\
     Put a breakpoint in \code{foobar.c}, line 42
-  \item \code{print var} or \code{print task->files[0].fd}\\
+  \item \code{print var} or \code{print task->files[0].fd} (\code{p})\\
     Print the variable \code{var}, or a more complicated reference. GDB
     can also nicely display structures with all their members
   \end{itemize}
@@ -352,7 +352,7 @@
     Continue the execution after a breakpoint
   \item \code{next} (\code{n})\\
     Continue to the next line, stepping over function calls
-  \item \code{step}\\
+  \item \code{step} (\code{s})\\
     Continue to the next line, entering into subfunctions
   \item \code{backtrace} (\code{bt})\\
     Display the program stack
@@ -488,12 +488,14 @@
   A tool to trace library calls used by a program and all the signals
   it receives
   \begin{itemize}
-  \item Very useful complement to strace, which shows only system
+  \item Very useful complement to \code{strace}, which shows only system
     calls.
   \item Of course, works even if you don't have the sources
   \item Allows to filter library calls with regular expressions, or
     just by a list of function names.
   \item Manual page: \url{https://linux.die.net/man/1/ltrace}
+  \item Works better with {\em glibc}. \code{ltrace} was broken
+	with {\em uClibc} and may still be.
   \end{itemize}
   See \url{https://en.wikipedia.org/wiki/Ltrace} for details
 \end{frame}
@@ -572,8 +574,8 @@ Process 17019 detached
   \end{itemize}
   Remote debugging
   \begin{itemize}
-  \item Set up remote debugging tools on the target: strace, ltrace\\
-    and gdbserver.
+  \item Set up remote debugging tools on the target:\\
+        \code{strace}, \code{ltrace} and \code{gdbserver}.
   \item Debug a simple application running on the target using remote
     debugging
   \end{itemize}