Cannot Find New Threads Generic Error Ubuntu
Contents |
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 gdb "thread debugging using libthread_db enabled" Stack Overflow the company Business Learn more about hiring developers or posting ads with
Suspend Error: Generic Error
us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a gdb libthread_db community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Cannot find new threads: generic error up vote 1 down vote favorite 1 When I
Unable To Find Libthread_db Matching Inferior's Thread Library
try to debug my C++ application using gdb, I get the following error: [Thread debugging using libthread_db enabled] Cannot find new threads: generic error If I try to quit gdb, I get A debugging session is active. Inferior 1 [process 17785] will be killed. I am not using any thread library myself. I tried the solutions suggested in gdb: Cannot find new threads: generic error but did not help. My cannot execute this command while the selected thread is running. OS: Ubuntu 10.04 $ gcc -v (Ubuntu 4.4.3-4ubuntu5) $ uname -a Linux rskDesktop 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:07:13 UTC 2011 x86_64 GNU/Linux Any suggestions? c++ debugging gdb share|improve this question edited Sep 27 '11 at 10:56 Kevin 2,84211747 asked Sep 27 '11 at 5:08 suresh 7031618 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote I am not using any thread library myself Take a look at this answer: reverse-step multithread error which should apply in your situation: force GDB not to activate thread debugging if you don't want it to be aware of the threads. (the EDIT applies as well, but maybe it's one of the libraries you use which requires the libpthread.so) share|improve this answer answered Sep 27 '11 at 10:37 Kevin 2,84211747 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged c++ debugging gdb or ask your own question. asked 5 years ag
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: http://stackoverflow.com/questions/7564463/cannot-find-new-threads-generic-error Sign up gdb: Cannot find new threads: generic error after system update up vote 4 down vote favorite I am running an OpenEmbedded based Linux on an ARM board, where my application is running. I used to run kernel 2.6.35, gdb 6.8 and gcc 4.3. Lately I've updated the system to kernel 2.6.37, gdb 7.4 (also tried 7.3) and gcc 4.6. Now, http://stackoverflow.com/questions/10840621/gdb-cannot-find-new-threads-generic-error-after-system-update my application can not be debugged anymore (on the ARM board), everytime I try to run it in gdb I get the error "gdb: Cannot find new threads: generic error". The application makes use of pthreads and does link against pthreads (readelf lists libpthread.so.0 as a dependency). The suggested solutions I found so far all recommend linking to pthread which I am already doing. The other recommendation I found was to use LD_PRELOAD=/lib/libpthread.so.0 which does not make any difference for me. Debugging the x86 builds of the application works without a problem. EDIT: To answer the questions posed in the first answer, I am using gdb on the target (ARM), i.e. no cross-gdb. I also have not stripped libpthread.so.0 (/lib/libpthread-2.9.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not stripped). glibc remained at version 2.9, and the update involved recompiling the whole linux image EDIT2: Removing /lib/libthread-db* allows debugging (with consequent warnings and obviously some features will not work) EDIT3: Using set debug libthread-db 1 I get: Starting program: /home/root/app Trying host libthread_db library: libthread_db.so.1
2 people Affects Status Importance Assigned to Milestone gdb (Ubuntu) Edit Invalid Undecided Unassigned Edit You https://bugs.launchpad.net/bugs/563361 need to log in to change this bug's status. Affecting: gdb (Ubuntu) Filed here by: Andreas Sandberg When: 2010-04-14 Completed: 2014-11-20 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status generic error Importance Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: gdb When debugging bug #423252 I noticed that GDB looses control over the target application cannot find new if it executes getpwnam when using libnss-ldap. GDB displays the following error message: [Thread debugging using libthread_db enabled] Cannot find new threads: generic error It is impossible to continue to work with the application after the above message has been displayed. For example, trying to execute 'next' results in the following error message: Cannot execute this command while the selected thread is running. I suspect this could actually be a kernel bug rather than a GDB bug (I've seen a fair deal of ptrace breakage at work), but I have no way of verifying that at the moment. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gdb 7.1-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic x86_64 Architecture: amd64 Date: Wed Apr 14 22:35:03 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdb Tags: amd64 apport-bug lucid Edit Tag help Andreas Sandberg (andysan) wrote on 2010-04-14: #