Bug 586478
| Summary: | GDB hangs when setting a breakpoint on a library not yet loaded | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dodji Seketeli <dodji> | ||||||
| Component: | gdb | Assignee: | Jan Kratochvil <jan.kratochvil> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 13 | CC: | jan.kratochvil, pmuldoon, swagiaal, tromey | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-02-02 20:38:29 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 409531 [details]
Second call stack taken after a longer hang/spinning period
I forgot to say that GDB hangs taking 100% CPU.
Arg, I made a little mistake in the steps to reproduce. In the end I said: b main b nemiver::DBGPerspective::execute_program It should rather be: b main run b nemiver::DBGPerspective::execute_program Sorry. I am having trouble reproducing this, but I also cant match the line numbers from the stack trace to the source from the rpm. Is it possible that you have another version of gdb interfering with the system installed one ? This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Last verification has been done on f12. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. (In reply to comment #1) > Created attachment 409531 [details] > Second call stack taken after a longer hang/spinning period > > I forgot to say that GDB hangs taking 100% CPU. Based on the stack trace, I would say that this has been fixed a long time ago. In the 7.0 time frame there was a bug where some kinds of namespace lookup took a lot of CPU. This was fixed in 7.1, IIRC. I am closing this on that basis. If you can still reproduce it with a newer gdb, please reopen and I will take a look. |
Created attachment 409530 [details] First call stack The problem happened when I was trying to debug Nemiver, using gdb-7.0.1-44.fc12.x86_64 on Fedora 12. I tried to write a little reproducer using dlopen/dlsym, but it worked fine in that case. So here is how you can get, compile, install Nemiver and reproduce the issue: yum install yum-utils yum-builddep nemiver git clone git://git.gnome.org/git/nemiver nemiver.git cd nemiver.git export NEMIVER_DEVEL=on ./autogen.sh make -j2 sudo make install cd tests gdb --args nemiver fooprog b main b nemiver::DBGPerspective::execute_program Trying to set the second breakpoint hangs GDB. I debugged GDB a bit and I could get some call stacks that are attached below.