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. It should be reproducible on any F20 box, but I may give any other info if you ask.
I can reproduce this. Does this occur with any other debuggers?
(In reply to Jon Ciesla from comment #1) > I can reproduce this. Does this occur with any other debuggers? At least for gdb it works OK (as I use gdb directly, I tried it just on simple int main() {} program). I haven't used ddd for any other language so far.
Seems to be a known issue but unresolved. Filed upstream bug. https://savannah.gnu.org/bugs/index.php?41649
Workaround from upstream bug: "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."
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.