KDevelop 4/Tips and tricks

From KDevelop

< KDevelop 4

[edit] How to add include paths to the parser ?

Add a .kdev_project file to the root directory of your project containing the paths that you want to parse.

[edit] How to debug kdevelop ?

For debugging kdevelop you'll need to do this (should be doable in .gdbinit):

set follow-fork-mode child
break <kdevelop>/app/main_internal.cpp:62
continue
.... (wait until it stops at main_internal.cpp)
set follow-fork-mode parent
continue

The reason is that if you enable follow-child once, gdb will also try to hook into other subprocesses like cmake or qmake runs being done. So you need to reset it once you're in the "real app". The follow-child is (obviously) needed to let gdb actually hook into the real app which loads everything.

Of course the envvar is still used and hence you can just as well do

KDEV_SESSION="uuid" gdb kdevelop.bin