[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #34882] dbx debugger mouseover "Run" command causes 100% CPU usage
From: |
Dave Mason |
Subject: |
[bug #34882] dbx debugger mouseover "Run" command causes 100% CPU usage |
Date: |
Wed, 23 Nov 2011 00:06:42 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 |
URL:
<http://savannah.gnu.org/bugs/?34882>
Summary: dbx debugger mouseover "Run" command causes 100% CPU
usage
Project: DDD
Submitted by: masey
Submitted on: Wed 23 Nov 2011 00:06:41 GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Release: None
_______________________________________________________
Details:
Confirmed with dbx version 7.7 on Solaris 10 u8.
*Workaround*
In DDD Preferences->General->Automatic Display of Button Hints turn off "as
Popup Tips" and "in the Status Line" checkboxes.
*Reason*
This is a bug in gdbTip function parsing the output of dbx command "commands"
looking for " run" as a command name. " run" now appears in the command
descriptions and parser goes into an infinite loop. Presumably this wasn't the
case with earlier versions of dbx.
_Fix Attached (diff for 3.3.12)_
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Wed 23 Nov 2011 00:06:41 GMT Name: dbxruncmdspin.diff Size: 395B By:
masey
Make sure parser always continues forward when searching for command
description.
<http://savannah.gnu.org/bugs/download.php?file_id=24430>
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34882>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #34882] dbx debugger mouseover "Run" command causes 100% CPU usage,
Dave Mason <=