There is a well known DDD bug that does not allow it to boot when the init file becomes corrupt.
This file is automatically created at directory .ddd, in the root user, with every boot. It must be erased each time it gets corrupted in order to run DDD.
Doing some tests, I noticed that this file is corrupted when you enter into the gdb "settings edit" menu. Reading a corrupted file "init" with text editor, I found several lines that begin with the word "set". Replacing occurrences of "set " with "! " (without quotes) makes the file operational without needing to erase it.
I am running Debian "wheezy" Linux on a Core i3 processor (64-bit). What is responsible for this strange behavior?