Gdb Error Initializing Thread_db Library

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the

Warning .dynamic Section For Is Not At The Expected Address (wrong Library Or Version Mismatch )

workings and policies of this site About Us Learn more about Stack solib-absolute-prefix Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs do you need "set solib-search-path" or "set sysroot" Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Remote Debugging multi-threaded C program with GDB up vote 0 down vote favorite 1 I am using Eclipse to develop and remotely debug some software for an ARM Processor. Unfortunately the software I am writing is multi-threaded and I am unable to debug it. If I place a break-point in the thread code, i get the following message: Child terminated with signal = 5 Child terminated with signal = 0x5 GDBserver exiting After doing quite a bit of Googling, I found a "solution" that proposed using this: strip --strip-debug libpthread.so.0 Unfortunately, I still get the termination errors. I would really appreciate your help in getting this figured out! Thanks! c multithreading eclipse gdb gdbserver share|improve this question edited Jun 13 '11 at 12:03 asked Jun 10 '11 at 13:46 avivas 1001216 I am not sure if this has something to do with multi threading as usually debugging it with gdb usually works fine. How have you called the strip command. The cc1.exe and gcc.exe prefixes are strange. I would call as a normal command in a bash. –dmeister Jun 10 '11 at 13:50 @dmeister This is the site where I found the "solution" http://sourceware.org/bugzilla/show_bug.cgi?id=8963 The way I called it was by adding that in the other flags part of the C builder in eclipse cause the call to be: arm-none-linux-gnueabi-gcc.exe -O0 -g3 -Wal

GDB from my x86 dev PC. I found a few people on the TI E2E forum struggling with the same issue, the solution was not immediately forthcoming on Google, but was found after a quick glance at the GDB reference card. Say you want to debug a dynamically linked executable with GDB, which is cross compiled and running on a remote target using gdbserver, you could get errors related to the loading of the shared object libraries when the program is set running. Here is the output with such errors that I got http://stackoverflow.com/questions/6307232/remote-debugging-multi-threaded-c-program-with-gdb during my debug session: On the development host: elangley@captainhook:~/voipboxdev/bsp/ltib-mpc8315erdb-20080630$ bin/gdb rootfs/nv/vapp GNU gdb 6.6.50.20070620-cvs Copyright (C) 2007 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This http://www.edlangley.co.uk/blog/2014/01/gdb-solib-absolute-prefix/ GDB was configured as "--host=i686-pc-linux-gnu --target=powerpc-linux". For bug reporting instructions, please see: bug-gdb@gnu.org. .. (gdb) target remote 192.168.7.2:4444 Remote debugging using 192.168.7.2:4444 warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. 0x0ffd7af8 in ?? () (gdb) b fprintf Breakpoint 1 at 0x1006c0c4 (gdb) c Continuing. Error while mapping shared library sections: linux-vdso32.so.1: No such file or directory. warning: .dynamic section for "/lib/libpthread.so.0" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections: /usr/lib/libsyslogr.so.0: No such file or directory. Error while mapping shared library sections: /usr/lib/libwatchdog.so.0: No such file or directory. warning: .dynamic section for "/usr/lib/libncurses.so.5" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections: /usr/lib/libvappif.so.0: No such file or directory. warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libdbus-1.so.3" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgobject-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgthread-2.0.so.0" is not at the expected address (wrong library

on broadcom MIPS problem --> "error initializing thread_db library" From: Mrukant Popat To: gdb at sourceware dot org Date: Fri, 15 Feb 2008 15:26:04 -0800 Subject: gdbserver https://sourceware.org/ml/gdb/2008-02/msg00110.html on broadcom MIPS problem --> "error initializing thread_db library" Reply-to: mpopat at pioneer-pra dot com hi folks, I have setup the debugging enviroment on Linux host using mipel-linux-gdb on i686 https://lists.nongnu.org/archive/html/ltib/2009-10/msg00028.html host and gdbserver on broadcom MIPS target. In this scenario, I am not using JTAG at all. My query is regarding debugging of multi-threaded application. Here are the steps I gdb error used to setup the environment. Also the kernel is booted thru tftp and filesystem is over NFS. 1) on target: gdbserver hostIP:5000 application_name (assuming I have installed all drivers and LD_LIBRARY_PATH is set correctly) 2) on host: ./mipsel-linux-gdb 3) on host: (gdb) file application_name 4) on host: (gdb) set solib-search-path : 5) on host: (gdb) target remote targetIP:5000 (the gdb error initializing target shows that host is now connected for debugging) 6) on host: (gdb) continue When I enter the command "continue" in mipsel-linux-gdb on host, it gives me many lines of warnings in gdbserver on targer --> "gdb: error initializing thread_db library" . Also when I again enter continue, then after some time the mipsel-linux-gdb on host give me this error --> "Program received signal SIG32, Real-time event 32. 0x2b03b224 in __rt_sigsuspend () from /opt/nfsroot_uclibc/images/7401c0/initramfs/lib/libc.so.0" This happens with all the multi-threaded applications. I tried to search in google and in one of the mailing list of busybox (gzip attached bcos that is what I got from google) this is what was written ###################--mail list start #################### /* mods for uClibc: __libc_sigaction is not in any standard headers */ >From andersen at codepoet.org Thu Oct 7 07:41:12 2004 From: andersen at codepoet.org (Erik Andersen) Date: Thu Oct 7 07:41:16 2004 Subject: [uClibc] gdb: error initializing thread_db library In-Reply-To: <5.1.0.14.2.20041007123250.4123a5a0@mail.beamex.com> References: <5.1.0.14.2.20040923095932.411f8da0@mail.beamex.com> <5.1.0.14.2.20041007123250.4123a5a0@mail.beamex.com> Message-ID: <20041007134112.GA21412@codepoet.org> On Thu Oct 07, 2004 at 12:46:24PM +0300, Caj Nordstr?m wrote: > > For some time a

User-agent: Thunderbird 2.0.0.16 (X11/20080707) Hi Vadim, I'm not sure. The only obvious questions are: 1/ Are you using the gdb in /bin 2/ Can you run this on it's own and get something sane from it (run version) 3/ Are all the parts of glibc on the target from the same origin (the toolchain normally made by base_libs). 4/ Is the executable on your host the actual one made by LTIB (i.e. from rpm/BUILD/xxx/.... 5/ Make sure you're not using an executable from rpm/BUILD/xxxx/ that is linking using the local .la files, these will pull in the wrong libraries from /usr/lib (maybe). You need to get a fully linked final executable that is not stripped. You can if necessary do this by putting this at the top of your .spec file making the package: %define __os_install_post %{nil} Regards, Stuart Vadim Lebedev wrote: While following the instructions: I'm getting follwing: on the target gdbserver :1234 /usr/bin/linphonec -d 6 -D Process /usr/bin/linphonec created; pid = 1008 Listening on port 1234 Remote debugging from host 192.168.10.85 gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread gdb: error initializing thread_db library: version mismatch between libthread_db and libpthread ============================ on the host: path ~/castel-gip/rootfs Execut