bugDDD - Bugs: bug #32949, "waiting until GDB gets...

 
 

bug #32949: "waiting until GDB gets ready" on Run

Submitter:  John Boncek <johnboncek>
Submitted:  Tue 29 Mar 2011 10:11:30 PM UTC
   
 
Category:  Gdb integration Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed Release:  3.3.11
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 28 Dec 2022 12:58:51 PM UTC, comment #2: 

fixed

Stefan Eickeler <eickeler>
Group administrator
Thu 10 Jul 2014 12:29:53 PM UTC, comment #1: 

Encountered this problem too. The easy solution as posted on Stackoverflow is to delete the init file in the ~/.ddd/ directory.

But that means all your customizations will be gone. So I started hunting for the real cause. I observed that the problem only occurs after I have used the "GDB Settings" dialog. Once you opened this dialog the init file mentioned above will grow because a lot of gdb settings will be stored there.

After shrinking those additional lines step by step I found the "offending line".
The problem is caused by the setting for extended-prompt. After opening the GDB settings dialog this line will read like

set extended-prompt not set\n\

This "not set" is what gdb will report on "show extended-prompt". Unfortunatley "set extended-prompt" is sort of buggy in gdb, so if I enter "set extended-prompt not set" in a gdb running from a shell without ddd involved gdb will lockup as well.

It looks like the only safe way of setting the extend-prompt is when it contains the string "(gdb)". So I modified the offending line in the init file and now it reads like this:

set extended-prompt (gdb) \n\

With this setting I do not encounter the problem any longer. Hope that helps in your case too.

Rainer König <rakoenig>
Tue 29 Mar 2011 10:11:30 PM UTC, original submission:  

When you run a program repeatedly using F2, DDD intermittently hangs for varying lengths of time with "Run: waiting until GDB gets ready" displayed, then sometimes continues and other times reports "GDB exited abnormally (segmentation fault)".  This tends to get worse (happens more often, with longer delays, and more chance of the abnormal exit) the more times you run a program during a single debugging session.

Problems in GDB may be implicated as well as (or instead of) in DDD.

John Boncek <johnboncek>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by eickeler (Posted a comment)
  • -email is unavailable- added by rakoenig (Posted a comment)
  • -email is unavailable- added by johnboncek (Submitted the item)
  • -email is unavailable- added by johnboncek
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-12-28 eickeler StatusNone Fixed
    2022-12-28 eickeler Open/ClosedOpen Closed
    2011-03-29 johnboncek Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-cf05.
    Corresponding source code