[FE training-materials-updates] sysdev-application-debugging: Give a workaround to use gdbserver

Gregory Clement gregory.clement at free-electrons.com
Thu Aug 28 18:54:38 CEST 2014

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

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


commit 0e1122383cf03e0597a9341dbb798f381f047d4e
Author: Gregory CLEMENT <gregory.clement at free-electrons.com>
Date:   Thu Aug 28 18:50:14 2014 +0200

    sysdev-application-debugging: Give a workaround to use gdbserver
    The libthread_db is the culprite when gdbserver hangs. So as a
    workaround, suggsest to remove it.
    Signed-off-by: Gregory CLEMENT <gregory.clement at free-electrons.com>


 labs/sysdev-application-debugging/sysdev-application-debugging.tex | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index f1f009a..36d3298 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -117,6 +117,12 @@ And tell gdb to connect to the remote system:
 (gdb) target remote <target-ip-address>:2345
+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.
 Then, use \code{gdb} as usual to set breakpoints, look at the source
 code, run the application step by step, etc. Graphical versions of
 gdb, such as \code{ddd} can also be used in the same way. In our case,

More information about the training-materials-updates mailing list