From the beginning of the Mac to now use Xcode, a period of time to an open source TestDisk from the text interface to a graphical interface. I think of a decision with Codeblocks + QT To do, mainly do not want to use QT own IDE, perhaps is accustomed to vc,codeblocks style, parameters on the setting is very convenient.
But in the code writing, found a problem, the Mac GDB can not be debugged, and later checked the original Apple is not allowed to debug other processes, need to set up a keychain. Although I set it up on the Internet, I still can't set it up on my computer. Every time I debug, I always quit, and sometimes it just crashes!
In view of the recent writing program in Ubuntu experience, I and it on the bar, when it is OK to ponder, this evening finally Kung Fu, let me solve. I see the debug log of Codeblock when I saw it debugging some parameters of the startup time and then I copied to the command line, I found that there is a problem with gdb parameters, and then found that Apple's own gcc, or g++ is clang. The GNU G++,GCC is not the usual one. And GDB also wood, and later found in the/opt/local/bin under a ggdb, there is a lldb, and then view the respective parameters, excluding lldb Apple's own debugging, with ggdb! Set the keychain, and then the familiar scene finally appeared.
Problems with Codeblocks debugging under Mac