Fixed A Bug When Initializing An Incompatible Version Of The Thread_db Library

 

You may receive an error that says there was an error initializing the thread_db library version mismatch. There are several steps you can take to fix this problem, so we’ll cover them shortly.

PC running slow?

1. Download ASR Pro from the website

2. Install it on your computer

3. Run the scan to find any malware or virus that might be lurking in your system

Improve the speed of your computer today by downloading this software - it will fix your PC problems.

 

 

Here’s a little tip for an issue I ran into recently when I decided to debug a VOIP stack on a boxed Power PC using GDB from my x86 development PC. I found several people struggling with their current issue on the TI E2E forum, the solution was not available on google in a very short time, but was found by looking at the GDB personal reference card.

Suppose you want to use GDB to debug a specific dynamically linked executable that is executed and compiled with gdbserver on a remote sleep. Here is the output of the obstacle type I got induring a debugging session:

From the GDB output, you will see that an attempt is made to interpret collections on the development host as candidates for dynamic inclusion in the compiled binary for PPC (“Warning: .dynamic section for” / usr / lib / â € â €), which is especially wrong. It looked like it was a bit bothersome for some debugging sessions as the program was outputting right after my breakpoint and the segment was wrong.

The tool sets the prefix solib-absolute, which tells GDB to check your local library built for the purpose, not a bunch of people on the host system. Here I select a prefix to indicate how LTIB created rootfs for the target:

Incidentally, this process is much clearer in newer versions of GDB. Above I used GDB 6.6 which is included in every Freescale BSP ltib that is very young.elangley @ captainhook: ~ / voipboxdev / bsp / ltib-mpc8315erdb-2080630 $ bin / gdb rootfs / NV / vappGNU gdb 6.6.50. (C) 20070620-CVSCopyright 2007 Free Software Foundation, Inc.GDB is free software released under the GNU General Public License in addition to who you are.You can change it, under certain conditions, by mail and / or copies.Enter “Specify by copy”, see Terms and Conditions.in fact, GDB makes no guarantees. Enter “View Warranty” for more details.This GDB has been configured although –target = powerpc-linux “” –host = i686-pc-linux-gnu.BugFor reporting instructions, see the following sections:[email protected]…(gdb) target remote 192.168.7.2:4444Remote debug from 192.168.7.2:4444Warning: The breakpoint of the dynamic linker function could not be found.GDB probably won’t be able to debug generic selection initializersand follow the loaded dynamic code explicitly.0x0ffd7af8 approximately ?? ()(gdb) b fprintfStop 1 at CContinuation 0x1006c0c4(GDB).Error in the included sections of the mapping library:linux-vdso32.so. # 1: this type of file or directory.Warning: There was no expected fix in the .dynamic section for creating “/lib/libpthread.so.0” (bad library or version in case of mismatch?)Mutual library section mapping error:/usr/lib/libsyslogr.so.0: no directory file.Failed to match shared sections:/ usr / lib / libwatchdog library.so.0: Such file or directory neo.Warning: dynamicthe section related to “/usr/lib/libncurses.so.5” is not in the expected location (bad library or version conflict?)Error while assigning displayed library sections:/usr/lib/libvappif.so.0: No file, more directory.Warning: dynamic section for “/usr/lib/libdbus-glib-1.so.2” does not use the expected address (invalid library or product conflict?)Warning: The dynamic section for “/usr/lib/libdbus-1.so.3” is in no way at the expected address (bad library or possibly incompatible version?)Warning: The .dynamic section for “/usr/lib/libgobject-2.0.so.0” is not at the expected address (wrong choice or version conflict?)Warning: The .dynamic section corresponding to “/usr/lib/libgthread-2.0.so.0” is not as expected (bad library or version conflict?)Warning: the .dynamic section to execute “/usr/lib/libglib-2.0.so.0” is not in the target (bad library or version conflict?)Warning: dynamic location ‘/lib/libc.so.6’ does not match expected address (invalid library or version conflict?)Error even though the shared library section mapping is correct:/lib/ld.so.No 1: What kind of database or directory.Warning: the dynamic section for “/lib/librt.so.1” is simply not at the expected address (bad research version or inconsistency?)Failed to match partitions with split variants:/usr/lib/libRCP.so.0: No file or directory.Errors even though shared library sections are highlighted:/usr/lib/libffi.so.6: There is no directory of this type, or possibly a file directory.Breakpoint 1 0x470c0Program with prefix received SIGSEGV, segmentation fault0x48031958 ?? ()(Gdb)

root @voipbox: ~ # / gdbserver *: 4444 / nv / vapp/ Na / vapp process is created; pid means 346Listening on port 4444Remote debugging from set 192.168.7.1gdb: error while initializing the thread_db library: version mismatch when connecting libthread_db and libpthreadgdb: error initializing local library thread_db: version mismatch between libthread_db and libpthreadgdb: Error initializing library thread_db: version mismatch considering libthread_db and libpthreadgdb: error while initializing the thread_db library: transcription mismatch between libthread_db and libpthreadgdb: Thread_db library initialization problems: libthread_db and, Hence, libpthreadgdb: error while initializing the thread_db library: label does not match between libthread_db and libpthreadgdb: error while initializing thread_db library: version mismatch between libthread_db and libpthreadgdb: error while initializing the thread_db library: version mismatch with libthread_db and libpthreadgdb: error initializing thread_db selection: version conflict between libthread_db and libpthread========VPort + D2Tech + VPORT VPORT_R_1_5_28======== D2 technology _ _ __ author | ‘/ / _ _ / _ _ _ / _ _ ._ _ /_.’/_ //_’/_ Across // //_///_//_////_’_n _ / Voice over IP products www.d2tech.com

(gdb) created solib-absolute-prefix ~ / voipboxdev / bsp / ltib-mpc8315erdb-2080630 / rootfs(gdb) b fprintfBreakpoint 1 on target 0x1006c0c4(gdb) remote 192.168.7.2:4444Remote debug from 192.168.7.2:44440x0ffd7af8 when? () from /home/elangley/voipboxdev/bsp/ltib-mpc8315erdb-2080630/rootfs/lib/ld.so.1(gdb) cSuite 1,Breakpoint 0x1006c0c4 in fprintf @ plt ()(Gdb)

elangley @ captainhook: ~ $ ./yocto_ppc_build_area/mybuilds/tmp/sysroots/x86_64-linux/usr/bin/ppc7400-poky-linux/powerpc-poky-linux-gdb voipboxdev / bsp / ltib-mp153030GNU gdb (GDB) 7.6Copyright (C) 2013 Free Foundation, Software Inc.GPLv3 + License: GNU gpl version 3 or higher or higher It is free software: your needs are free change and transfer.Often NO WARRANTY is required by law. Enter “Show Copies”and “See warranty ”for more information.This GDB is configured according to “–host = x86_64-linux –target = powerpc-poky-linux”Declaration information can be found at the following address: …Reading characters from / mnt / src / bsp / ltib-mpc8315erdb-2080630 / rootfs / nv / vapp … done.(gdb) target remote 192.168.7.2:4444Remote debugging using 192.168.7.2:4444Warning: Could not find a compelling linker function breakpoint.GDB cannot help debug shared library initializersand explicitly follow the loaded variable code.0x0ffd7af8 in ?? ()(gdb) b fprintfStop 7 at CContinuation 0x1006c0c4(GDB).Warning: Unable to load library symbols used for libraries 16 such as linux-vdso32.so.1.Use most of the shared library information command to view this complete list.Do you need “set solib-search-path” “set and for sysroot”?Breakpoint 1, 0x1006c0c4 in fprintf @ plt ()(Gdb)

 

 

Improve the speed of your computer today by downloading this software - it will fix your PC problems.