Home > gdb cannot > gdb cannot initialize thread debugging library generic error

Gdb Cannot Initialize Thread Debugging Library Generic Error

initialize thread debugging library: generic error From: srinivas bakki To: gdb at sourceware dot org Date: Wed, 8 Aug 2007 08:01:06 +0100 (BST) Subject: Cannot initialize thread debugging library: generic error Hi, I have compiled my toolchain with binutils-2.17.50.0.14, GCC 3.4.6 and uClibc-0.9.28 using buildroot. I build the gdb with this toolchain. The debugger starts up well and am able to do all the basic debugging including handling the signals. However am not able to debug threads. When i run the test program in teh debugger it throws up following warnings: Cannot initialize thread debugging library: generic error I searched the net for similar messages, i found similar warnings with gdb but in the context of using insight. Still i tried setting the solib-absolute-prefix to /. , it doesnt work. Any help on this please ? Regards Srinivas Bakki ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html Follow-Ups: Re: Cannot initialize thread debugging library: generic error From: Ramana Radhakrishnan Index Nav: [DateIndex] [SubjectIndex] [AuthorIndex] [ThreadIndex] Message Nav: [DatePrev][DateNext] [ThreadPrev][ThreadNext]

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs 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 Unable to Debug Multi-Threaded Application with gdb up vote 11 down vote favorite 1 I am debugging a multi-threaded application with gdb, but https://www.sourceware.org/ml/gdb/2007-08/msg00078.html when I start the program in gdb I get the warning: warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. I can still debug, but I can't debug anything other than the main thread. I have read forums that suggest installing the packages libthread-db1 and glibc-dbg, but this does not correct the problem for me. On my machine I have the 3 files /lib/libthread_db.so.1, /lib/.debug/libthread_db-1.0.so, and /lib/libthread_db-1.0.so. I tried http://stackoverflow.com/questions/11585472/unable-to-debug-multi-threaded-application-with-gdb creating symbolic links in /lib with the name libthread_db.so, one time pointing at the /lib/libthread_db.so.1 file, and another time pointing at the /lib/libthread_db-1.0.so file, and also I created the symbolic link /lib/.debug/libthread_db.so pointing to /lib/.debug/libthread_db-1.0.so, all with no luck. In gdb I have tried setting libthread-db-search-path to /lib (with the symlink once set to libthread_db.so.1, and once to libthread_db-1.0.so, and also set to /lib/.debug. Any suggestions? I am using Angstrom Linux v2.6.39 for the BeagleBoard-xm. multithreading debugging gdb beagleboard angstrom-linux share|improve this question edited Jul 8 at 14:13 asked Jul 20 '12 at 19:02 Samuel 1,47911827 Note that I started with a root file system from a 2.6.32 kernel (Angstrom-Beagleboard-demo-image-glibc-ipk-2011.1-beagleboar‌d.rootfs.tar.bz2), and copied the linux source into /usr/src, and cross-compiled a new kernel based on 2.6.39. This is likely the reason for the version mismatch. I have the threading shared object files from the cross compiler, and I tried replacing the existing .so files with the ones from the cross compiler, but it caused make to crash. Any ideas? –Samuel Jul 23 '12 at 15:00 1 Hi I'm currently having the exact same issue on angstrom running on a beaglebone. Did you ever figure out the solution? –Brandon Yates Jun 19 '13 at 23:30 Also, be sure your version of libpthread is not stripped –Pavel Krasavin Jul

This bug is not in your last search results. Bug15782 - Apache segfaults https://bz.apache.org/bugzilla/show_bug.cgi?id=15782 at startup Summary: Apache segfaults at startup Status: CLOSED WORKSFORME Product: Apache httpd-1.3 Classification: Unclassified Component: core Version: 1.3.27 Hardware: Macintosh Linux Importance: P3 normal (vote) TargetMilestone: --- http://blog.vinceliu.com/2009_09_01_archive.html Assigned To: Apache HTTPD Bugs Mailing List URL: Keywords: Depends on: Blocks: Show dependency tree Reported: 2003-01-03 15:33 UTC by Damien Pollet Modified: 2004-11-16 19:05 UTC gdb cannot (History) CC List: 0 users Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Damien Pollet 2003-01-03 15:33:34 UTC gcc 3.2.1, glibc 2.3.1 (see bug 15781 of apache httpd-2.0) fallawater tmp # gdb apache GNU gdb 5.2.1 Copyright gdb cannot initialize 2002 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 GDB was configured as "powerpc-unknown-linux-gnu"...(no debugging symbols found)... (gdb) run Starting program: /mnt/raid/usr/sbin/apache (no debugging symbols found)...warning: Cannot initialize thread debugging library: generic error (no debugging symbols found)...warning: Cannot initialize thread debugging library: generic error (no debugging symbols found)...warning: Cannot initialize thread debugging library: generic error (no debugging symbols found)...warning: Cannot initialize thread debugging library: generic error (no debugging symbols found)...warning: Cannot initialize thread debugging library: generic error (no debugging symbols found)...warning: Cannot initialize thread debugging library: generic error Program received signal SIGSEGV, Segmentation fault. 0x0fd43a9c in __ctype_b_loc () from /lib/libc.so.6 (gdb) bt #0 0x0fd43a9c in __ctype_b_loc () from /lib/libc.so.6 #1 0x0fd43ab8 in __ctype_b_loc () from /lib/libc.so.6 #2 0x1000cf1c in ap_pvsprintf () #3 0x1000d00

more proper to call it a Debian package given its lineage. Nevertheless the mechanism behind building your own packages is pretty much the same for the two.I'll use GDB as an example of how to build your own package - for a good reason, firstly because the stock version of GDB that is shipped with Ubuntu is terribly broken. Here's what I mean:% gdb --args javaGNU gdb 6.8-debianCopyright (C) 2008 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. Type "show copying"and "show warranty" for details.This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)(gdb) rStarting program: /usr/bin/java Test(no debugging symbols found)(no debugging symbols found)(no debugging symbols found)(no debugging symbols found)[Thread debugging using libthread_db enabled][New process 16487]Executing new program: /usr/lib/jvm/java-6-openjdk/jre/bin/javawarning: Cannot initialize thread debugging library: generic errorwarning: Cannot initialize thread debugging library: generic errorwarning: Cannot initialize thread debugging library: generic errorwarning: Cannot initialize thread debugging library: generic error[New process 16487][Thread debugging using libthread_db enabled]Segmentation faultThe stock build of GDB doesn't handle multi-threaded applications properly, among other minor issue like not setting the path to point to the correct debug library paths, which makes it unusable for serious debugging tasks.Secondly, GDB 7.0 has reversible debugging, which makes it doubly tempting to roll my own. Finally, GDB has minimal external and library dependencies, which is an easy example to build a package without going into the complexity of having to generate a chrooted environment.But why not just do the typical 'configure && make install' combination?The drawback in doing so, is that the process is one-way: once you've installed it like that, there is no easy way of uninstalling it, short of remembering the list of what's being installed and removing them manually. Do-able? Sure, but certainly cumbersome. The neater way to do this is to create a package and have the package manager deal with installation/uninstallation for you.Building GDBWe need to perform the usual compiling and installing steps like we normally do; the only

 

Related content

error accessing memory address bad address

Error Accessing Memory Address Bad Address table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Error Accessing Memory Address a li li a href Gdb Cannot Insert Breakpoint Cannot Access Memory At Address a li li a href Gdb Break Cannot Access Memory At Address a li ul td tr tbody table p Bug - breakpoint Error accessing memory address Summary breakpoint Error accessing memory address Status ASSIGNED relatedl Alias None Product gdb Classification Unclassified Component breakpoints show error accessing memory address input output error other bugs Version Importance P

error accessing memory address gdb

Error Accessing Memory Address Gdb table id toc tbody tr td div id toctitle Contents div ul li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Gdb Cannot Insert Breakpoint a li ul td tr tbody table p Bug - breakpoint Error accessing memory relatedl address Summary breakpoint Error accessing memory address gdb cannot insert breakpoint error accessing memory Status ASSIGNED Alias None Product gdb Classification Unclassified Component breakpoints gdb error accessing memory address input output error show other bugs Version Importance P critical Target Milestone --- Assignee Not yet assigned to

error accessing memory address 0x0 input/output error

Error Accessing Memory Address x Input output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Error Accessing Memory Address a li li a href Gdb Break Cannot Access Memory At Address a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p last months will be deleted periodically to fight SPAM Home Help Search relatedl Login Register Wiki Code Blocks User forums Help p h id Gdb Cannot Insert Breakpoint Error Accessing Memory Address p GDB having problems setting breakpoints

error accessing memory address 0x1 input/output error

Error Accessing Memory Address x Input output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint a li ul td tr tbody table p Bug - breakpoint Error accessing memory address Summary breakpoint Error accessing memory address Status ASSIGNED relatedl Alias None Product gdb Classification Unclassified Component breakpoints show p h id Gdb Cannot Insert Breakpoint p other bugs Version Importance P critical Target Milestone --- Assignee Not yet gdb cannot access memory at address assigned to anyone URL Keywords Depends on Blocks Reported - - UTC by desimoi

error accessing memory address 0x0

Error Accessing Memory Address x table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Error Accessing Memory Address a li li a href Gdb Break Cannot Access Memory At Address a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p here for a quick overview of the site Help Center Detailed answers to any questions you might relatedl have Meta Discuss the workings and policies of this site p h id Gdb Cannot Insert Breakpoint Error Accessing Memory Address p About

error accessing memory address 0x0 invalid argument

Error Accessing Memory Address x Invalid Argument table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Cannot Access Memory At Address a li li a href Gdb Break Cannot Access Memory At Address a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li ul td tr tbody table p Things Small and Medium Business Service Providers All Solutions Services Advise Transform and Manage Financing and Flexible Capacity IT Support Services Education relatedl and Training Services All Services Products Integrated Systems gdb cannot insert breakpoint

gdb error accessing memory address i o error

Gdb Error Accessing Memory Address I O Error table id toc tbody tr td div id toctitle Contents div ul li a href Warning Cannot Insert Breakpoint a li ul td tr tbody table p Bug - breakpoint Error accessing memory address Summary breakpoint Error accessing memory relatedl address Status ASSIGNED Alias None Product gdb Classification gdb cannot insert breakpoint Unclassified Component breakpoints show other bugs Version Importance P critical Target p h id Warning Cannot Insert Breakpoint p Milestone --- Assignee Not yet assigned to anyone URL Keywords Depends on Blocks Reported - - UTC gdb cannot access memory

gdbserver input/output error

Gdbserver Input output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Error Accessing Memory a li li a href Gdb Cannot Insert Breakpoint a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta relatedl Discuss the workings and policies of this site About Us p h

gdb cannot insert breakpoint error accessing memory address

Gdb Cannot Insert Breakpoint Error Accessing Memory Address table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Break Cannot Access Memory At Address a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p here for a quick overview of the site Help Center Detailed relatedl answers to any questions you might have Meta Discuss gdb cannot insert breakpoint cannot access memory at address the workings and policies of this site

gdb warning restore memory write failed input/output error

Gdb Warning Restore Memory Write Failed Input output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Break Cannot Access Memory At Address a li li a href Gdb Cannot Insert Breakpoint a li li a href Warning Cannot Insert Breakpoint a li ul td tr tbody table p Things LocationTech Long-Term Support PolarSys Science OpenMDM More Community Marketplace Events Planet Eclipse Newsletter Videos Participate Report a Bug Forums Mailing Lists Wiki IRC How relatedl to Contribute Working Groups Automotive Internet of Things LocationTech Long-Term gdb cannot insert breakpoint error accessing memory

gdb error accessing memory address unknown error

Gdb Error Accessing Memory Address Unknown Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p to check the gdb cannot insert breakpoint nightly builds in the forum Home Help Search Login cannot access memory at address gdb breakpoint Register Wiki Code Blocks User forums Help GDB having problems setting warning cannot insert breakpoint breakpoints laquo previous next raquo Send this topic Print Pages Go Down Author Topic GDB having problems setting breakpoints Read p h id Gdb Cannot Access

gdb cannot insert breakpoint input output error

Gdb Cannot Insert Breakpoint Input Output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Break Cannot Access Memory At Address a li li a href Gdb Cannot Insert Breakpoint a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li ul td tr tbody table p Windows and many major Linux distros here gdb cannot insert breakpoint cannot access memory at address Home Help Search Login Register Wiki Code Blocks p h id Gdb Break Cannot Access Memory At Address p User forums Help GDB having

gdb cannot insert breakpoint error accessing

Gdb Cannot Insert Breakpoint Error Accessing table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Error Accessing Memory Address a li li a href Gdb Cannot Insert Breakpoint a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p Forgot Password Login relatedl x Bug - Error accessing memory address p h id Gdb Cannot Insert Breakpoint Error Accessing Memory Address p when creating JIT internal breakpoint Summary

gdb error accessing memory address bad address

Gdb Error Accessing Memory Address Bad Address table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Error Accessing Memory a li li a href Gdb Cannot Insert Breakpoint a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies relatedl of this site About

gdb input/output error

Gdb Input output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Break Cannot Access Memory At Address a li li a href Gdb Cannot Insert Breakpoint a li li a href Warning Cannot Insert Breakpoint a li ul td tr tbody table p here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the relatedl workings and policies of this site About Us Learn more gdb cannot insert breakpoint error accessing memory about Stack Overflow the company Business Learn more about

gdb cannot insert breakpoint error accessing memory address input/output error

Gdb Cannot Insert Breakpoint Error Accessing Memory Address Input output Error table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint Cannot Access Memory At Address a li li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Warning Cannot Insert Breakpoint a li ul td tr tbody table p insert breakpoint - From Anmol P Paralkar anmol at freescale dot com To gdb at sourceware dot org Date relatedl Fri Jul - CDT p h id Gdb Cannot Insert Breakpoint Cannot Access Memory

gdb error accessing memory address operation not permitted

Gdb Error Accessing Memory Address Operation Not Permitted table id toc tbody tr td div id toctitle Contents div ul li a href Error In Re-setting Breakpoint Cannot Access Memory At Address a li li a href Warning Cannot Insert Breakpoint a li ul td tr tbody table p here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site relatedl About Us Learn more about Stack Overflow the company Business Learn gdb cannot insert breakpoint error accessing memory address more about hiring developers

qt error accessing memory address

Qt Error Accessing Memory Address table id toc tbody tr td div id toctitle Contents div ul li a href Gdb Cannot Insert Breakpoint a li li a href Gdb Cannot Access Memory At Address a li ul td tr tbody table p template code Attempting to do so while debugging causes Qt Creator to hang Agile Board ExportXMLWordPrintable Details Type Bug Status Closed Priority Not Evaluated relatedl Resolution Out of scope Affects Version s Qt Creator p h id Gdb Cannot Insert Breakpoint p Fix Version s None Component s Debugger Labels None Environment Windows Vista Description I warning