QtForum.org »
QtForum.org » Qt »
KDE Development »Dear visitor, welcome to QtForum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Friday, January 26th 2007, 9:23pm
Quoted
Originally posted by sunil.thaha
Probably because that break point is never met. Or maybe because you have not installed gdb. Why don't you try debugging a simple C++ program and see if the debugging really happens. Another thing that came to my mind was that you might be setting bookmarks ( F2 shortcut ) instead of Break point ( red in color ).
Friday, June 22nd 2007, 2:47am
. I'll have to find out why it did that but adding another break point on that line made it step properly into the loop after words and onto the end.. Guess I'll have to learn the syntax of a .pro file. Oh well, such is life and you can't complain seeing as KDevelop is as good as it is 
.
Wednesday, August 29th 2007, 6:36am
Originally posted by marquedios
Editing the <project name>.pro and adding the CONFIG += debug made KDevelop 3.4.0 running on KDE 3.5.6 crash. However if I edit the already existing CONFIG line:
CONFIG += warn_on \
qt \
thread
to read:
CONFIG += warn_on \
qt \
thread \
debug
Then editing the src\src.pro file and adding the line:
CONFIG += debug
Debugging works. I found though that using the same technique for the src.pro file as I did the <project name>.pro file also made KDevelop crash...
Thursday, March 26th 2009, 8:46am
The posts below are two years old now, but the issue is important. It relates to the inability of a fairly experienced coder to get the debugger in kdevelop working.
It turns out that Dr Mega was almost certainly compiling his (really simple) C++ source code correctly. But to run the program he would have used the menu entry /Build/Execute program (or Shift+F9). It turns out that to get the debugger working, in kdevelop you must instead use the menu item, /Debug/Start (or F9).
That is actually serious. I was stymied by this for half an afternoon, before duplicating Dr Mega's source as a kdevelop project, registering here, and thinking rather hard about all the kdevelop menus. It was quite simply a show-stopper, and if two fairly experienced (but not in kdevelop) coders could be shut down in this manner, kdevelop will turn off a number of otherwise quite enthusiastic users.
Is it possible to incorporate some obvious warning, like instead of having "Execute Program" in the menu, something like "Run without debug"? The way kdevelop splits the debug function from an ordinary run function needs to be more widely disseminated.
Originally posted by sunil.thaha
Probably because that break point is never met. Or maybe because you have not installed gdb. Why don't you try debugging a simple C++ program and see if the debugging really happens. Another thing that came to my mind was that you might be setting bookmarks ( F2 shortcut ) instead of Break point ( red in color ).
The breakpoint would always be met. My test program couldn't get any simpler really (look at the code I posted in my original note). I'm not sure what gdb is (presumably its the linux standard debugger??) but I have since learned that there is a debugger installed on my machine because I've stopped using KDevelop in favour of Anjuta, which does most of what I need and the debugger worked exactly as I would have expected.
