Ubuntu
gdb package

spawned a gdb spinning at 100%CPU

Bug #434168 reported by Kiri
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I discovered a gdb process that was consuming all CPU time and killed it.
At that time, a new apport window opened to report a bug.
I am guessing the gdb process was started by apport.
If it happens again, I will check in pstree.

Revision history for this message
Kiri (kiri) wrote :

I had this reoccur. When you kill the apport window, GDB stays running in the background.

Bug #452807 is a duplicate of this bug.
Bug #442249 looks like a duplicate.

I checked the core file as described in Bug #452807 and have the same error message from GDB.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message
Martin Pitt (pitti) wrote :

apport already calls gdb with 'set backtrace limit 2000', if gdb is still in an endless loop, that's a gdb bug. Reassigning.

affects: apport → gdb (Ubuntu)
Launchpad Janitor (janitor)
Changed in gdb (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

closing this rather old issue. sorry for not addressing this earlier. Please could you recheck with the recent 14.04 LTS or 14.10 releases and reopen the issue if the problem persists?

Changed in gdb (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.