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.
https://savannah.gnu.org/bugs/?29717
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:
https://savannah.gnu.org/bugs/?29717
The "DDD_remake_repairs_attempt2.patch" is here:
https://savannah.gnu.org/bugs/download.php?file_id=31090
|