[FE training-materials-updates] Merge branch 'master' of git.free-electrons.com:training-materials

[maxime.ripard at free-electrons.com]

- Log -----------------------------------------------------------------
http://git.free-electrons.com/training-materials/commit/?id=f23e39802ff877409c710799cfff6b581912c41a

commit f23e39802ff877409c710799cfff6b581912c41a
Merge: 609ba27 5244b41
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Wed Feb 29 15:08:23 2012 +0100

    Merge branch 'master' of git.free-electrons.com:training-materials


http://git.free-electrons.com/training-materials/commit/?id=609ba27a5bb716902f9da6f44c632f702c8b3e24

commit 609ba27a5bb716902f9da6f44c632f702c8b3e24
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Wed Feb 29 15:07:43 2012 +0100

    Remove ltrace from slides since it doesn't work anymore

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 96e89b3..71c116c 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -1,5 +1,7 @@
-\subchapter{Remote application debugging}{Objective: Use strace and
-  ltrace to diagnose program issues. Use gdbserver and a
+%\subchapter{Remote application debugging}{Objective: Use strace and
+%  ltrace to diagnose program issues. Use gdbserver and a
+\subchapter{Remote application debugging}{Objective: Use strace
+  to diagnose program issues. Use gdbserver and a
   cross-debugger to remotely debug an embedded application}
 
 \section{Setup}
@@ -11,9 +13,11 @@ Go to the \code{/home/<user>/felabs/sysdev/debugging} directory.
 Boot your ARM board over NFS on the filesystem produced in the {\em
   Tiny embedded system} lab, with the same kernel.
 
-\section{Setting up gdbserver, strace and ltrace}
+%\section{Setting up gdbserver, strace and ltrace}
+\section{Setting up gdbserver and strace}
 
-\code{gdbserver}, \code{strace} and \code{ltrace} have already been
+%\code{gdbserver}, \code{strace} and \code{ltrace} have already been
+\code{gdbserver} and \code{strace} have already been
 compiled for your target architecture as part of the cross-compiling
 toolchain. Find them in the installation directory of your
 toolchain. Copy these binaries to the \code{/usr/bin/} directory in
@@ -84,14 +88,14 @@ code!
 Now add what the program was waiting for, and now see your program
 proceed to another bug, failing with a segmentation fault.
 
-\section{Using ltrace}
+%\section{Using ltrace}
 
-Try to run the program through \code{ltrace}. You will see that
-another library is required to run this utility. Find this library in
-the toolchain and add it to your root filesystem again.
+%Try to run the program through \code{ltrace}. You will see that
+%another library is required to run this utility. Find this library in
+%the toolchain and add it to your root filesystem again.
 
-Now, ltrace should run fine and you should see what the program does:
-it tries to consume as much system memory as it can!
+%Now, ltrace should run fine and you should see what the program does:
+%it tries to consume as much system memory as it can!
 
 \section{Using gdbserver}
 
@@ -174,7 +178,8 @@ During this lab, we learned that...
   used.
 
 \item It's easy to study the behavior of programs and diagnose issues
-  without even having the source code, thanks to strace and ltrace.
+%  without even having the source code, thanks to strace and ltrace.
+  without even having the source code, thanks to strace.
 
 \item You can leave a small \code{gdbserver} program (300 KB) on your target
   that allows to debug target applications, using a standard GDB

-----------------------------------------------------------------------

Summary of changes:
 .../sysdev-application-debugging.tex               |   27 +++++++++++--------
 1 files changed, 16 insertions(+), 11 deletions(-)