bugDDD - Bugs: bug #41649, Unable to run bashdb via ddd,...


bug #41649: Unable to run bashdb via ddd, 3.3.12

Submitted by:  Gwyn Ciesla <limburgher>
Submitted on:  Thu 20 Feb 2014 06:54:31 PM UTC  
Category:  Bashdb integration Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  None

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Mon 11 Jun 2018 02:37:54 PM UTC, comment #6: 

I confirm this is a regression introduced in 3.3.12. The last version to feature working support for `bashdb` and `remake` was 3.3.11.

Will try to locate the exact commit with `git bisect`.

Andrey ``Bass`` Shcheglov <bass>
Wed 16 Apr 2014 10:37:11 PM UTC, comment #5: 

Hi there,

I think the reason you're not getting any email notification is that your original post and this newer post were made as anonymous.

Ie, you weren't logged in at the time. If you were, the system here seems to automatically add you into the cc-list.

So you can either:

a) log-in prior to your next post
b) Go to the "Mail Notification Carbon-Copy List" section further below and add your email/user-login there and click 'Submit Changes'

Hmm, if 1) didn't work, then I'm stumped.

I recall Rocky Bernstein (creator of remake/bashdb) mentioned that the preivous maintainer of ddd here passed away, and nobody has taken his place yet.

That's why these forums seem very quiet of late, many questions going un-answered.

So you might have to resort to stepping through the ddd source with gdb and seeing where it falls over for you, patch it up, and maybe share your patch here too, if you feel it'll help others in a similar gripe :)

Gurce Isikyildiz <gurce>
Project Member
Wed 16 Apr 2014 10:19:36 PM UTC, comment #4: 

[ the registration mail did not make up it up to now. Is the mailserver down or blacklisted?]

I can safely rule out (1) now, thanks for the suggestion .
If that runs fine on your machine, (2) should'nt be directly responsible for this issue. However I read somewhere that ddd communicates with gdb and others using a special shell-like protocol (whose name I forgot :X).
As the kernel and overall system is very old it might be an issue with new gdb + old shell + new ddd, just an idea. Does that make sense? (digging in the dark ;-))

Tue 15 Apr 2014 12:42:55 AM UTC, comment #3: 

Hmm, I can't say for sure, but this could possibly be a similar issue to the remake+ddd failure I looked into a month ago.


In that case, I recall ddd also stalling on the "Opening session..." message.

After studying/debugging the ddd source a bit, it turned out to be due to the console-prompt for remake changing in newer versions.

From: mdb<...> 
To: remake<...>

(I think remake used to be called 'make debugger', hence the old abbreviation of mdb)

By console-prompt, I'm referring to remake's prompt, used to let the user know they can type a command in after it.

Ddd was parsing the output of the remake app, looking for this prompt, in order to indicate that the session was finally 'opened'.

So due to the name-change of the remake prompt in the newer version, ddd never found the old-prompt, so just got stuck in this "opening session" state and could never open it.

So in your case with ddd+gdb, could something similar have happened?

You mentioned that you're using gdb 7.7.

I'm currently using gdb 7.5 (with ddd 3.3.12), and these two are running fine for me, the session opens fine.

So it makes me wonder if there were any changes to the command-prompt for gdb between my version and yours that could be causing the same issue I saw in remake.

Some possibilities might be to:

1) Downgrade gdb, to perhaps 7.5?

2) If you want to soldier on with gdb7.7 and patch up ddd to work with it, you could take a look at the patch I made for ddd+remake, to get some idea of which bits of the code to tweak.

The remake+ddd bug-post is here:


The "DDD_remake_repairs_attempt2.patch" is here:


Gurce Isikyildiz <gurce>
Project Member
Mon 14 Apr 2014 09:25:47 PM UTC, comment #2: 

I have the same problem though I don't use bashdb - I guess it's more of a session issue than tied to a particular debugger.

My ddd starts and hangs up indicating "Opening session .ddd". cleaning ~/.ddd doesn't help.

I have the following configuration:
ddd 3.3.12
gdb 7.7
Linux bt 2.6.20-BT-PwnSAuce-NOSMP [...] i686 i 686 i 386 GNU/Linux
(this version is old on purpose)

(initially I had an older version. I chose the newest ones and compiled them to make sure it isn't fixed in the current release).


gdb does work properly, so that's no issue.
Quirk of fate: it's DVL where ddd doesn't work. Or I'm even more of a noob than I thought ;-)

(I have registered about 10 minutes ago but the registration mail hasn't made it yet.)

Tue 25 Mar 2014 09:06:22 AM UTC, comment #1: 

I've been experiencing the same thing.

I did notice though that (for some strange reason) if I type "exit" in the lower-pane of ddd, this seems to kill one instance of bashdb, and then another instance of bashdb seems to run.

This 2nd instance of bashdb seems to play more nicely within ddd, with the bash-script source finally appearing in the top-pane and allowing you to step-through and debug.

Perhaps this can be a workaround for now.

Gurce Isikyildiz <gurce>
Project Member
Thu 20 Feb 2014 06:54:31 PM UTC, original submission:  

When I run:

  ddd --debugger /usr/bin/bashdb ANY_SCRIPT

... ddd always hangs on 'Openning session "some_hash"'.

I have no ~/.ddd directory before I start ddd and no ~/.gdbinit file so
everything should be clean. 


Gwyn Ciesla <limburgher>


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

Attach Files:

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 bass (Posted a comment)
  • -email is unavailable- added by gurce (Posted a comment)
  • -email is unavailable- added by limburgher (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    No changes have been made to this item

    Back to the top

    Powered by Savane 3.7