[FE training-materials-updates] sysdev-application-debugging: ltrace is no more broken

[Gregory Clement]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=66b1a2640eb27ab7d7a72aa71e75459c4698f593

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

commit 66b1a2640eb27ab7d7a72aa71e75459c4698f593
Author: Gregory CLEMENT <gregory.clement at free-electrons.com>
Date:   Fri Sep 2 17:56:12 2016 +0200

    sysdev-application-debugging: ltrace is no more broken
    
    With buildroot 2016.02 ltrace works again.
    
    Signed-off-by: Gregory CLEMENT <gregory.clement at free-electrons.com>


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

66b1a2640eb27ab7d7a72aa71e75459c4698f593
 labs/sysdev-application-debugging/sysdev-application-debugging.tex | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 1cab48e..d79f4c9 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -53,11 +53,8 @@ proceed to another bug, failing with a segmentation fault.
 
 Now run the program through \code{ltrace}.
 
-Unfortunately, the latest version of \code{ltrace} currently looks broken,
-at least with the uClibc version that we are using.
- 
-It it works, you could see all the library calls that the program does:
-it tries to consume as much system memory as it can!
+Now you should see what the program does: it tries to consume as much
+system memory as it can!
 
 \section{Using gdbserver}