[FE training-materials-updates] debugging: timeout isn't the only error you might get from gdb

[Maxime Ripard]

Repository : git://git.free-electrons.com/training-materials.git

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

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

commit a1ecdf38a128532f8ccd983fd9d3917989741131
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Fri Aug 29 11:28:59 2014 +0200

    debugging: timeout isn't the only error you might get from gdb
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

a1ecdf38a128532f8ccd983fd9d3917989741131
 .../sysdev-application-debugging.tex                          | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 36d3298..716f1e7 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -117,11 +117,12 @@ And tell gdb to connect to the remote system:
 (gdb) target remote <target-ip-address>:2345
 \end{verbatim}
 
-If at this point you received timeout message and if the gdbserver is
-stuck, then you will have to remove \code{/lib/libthread_db.so.1} from
-the target. This library allows multithread debugging but this library
-is currently buggy for our configuration. Fortunately we don't have
-to debug a multithread application.
+If at this point you received timeout or packet error messages and if
+the gdbserver is stuck, then you will have to remove
+\code{/lib/libthread_db.so.1} from the target. This library allows
+multithread debugging but this library is currently buggy for our
+configuration. Fortunately we don't have to debug a multithread
+application.
 
 Then, use \code{gdb} as usual to set breakpoints, look at the source
 code, run the application step by step, etc. Graphical versions of