Howto debug KDE CVS application ?

[Thomas McGuire]

Hello,

I want to debug a KDE CVS application (KGet), but I can not get it to work.
My source directory of kdenetwork is /home/tmg/src/kde/kdenetwork,
my build directory /home/tmg/src/kde/build_debug/kdenetwork and 
my KDE directory /home/tmg/kde_debug.

As described in the "How to use KDevelop with KDE CVS"-Guide I used 
"Project->Import existing project" to import the whole kdenetwork module.
Afterwards I set KGet as the active target.
Then I set "Build directory" in "Configure Options" to 
/home/tmg/src/kde/build_debug/kdenetwork.
In "Run Options", I set the following things:
"Main program" to /home/tmg/src/kde/build_debug/kdenetwork/kget/kget
"Custom directory" to /home/tmg/src/kde/build_debug/kdenetwork/kget/

I hope all these settings are correct, but I don't know for sure.

Now strange things happen when I execute the program:
In the application output tab, the message "*** Exited normally ***" is 
shown soon after starting it, but KGet is still running.
Because of this, I can not debug. If I set a breakpoint, gdb
confirms that with
>Breakpoint 1 at 0x80699b0: 
file /home/tmg/src/kde/kdenetwork/kget/transferlist.cpp, line 266,
but exits shortly after this with
>Detaching after fork from child process 11219.
>Program exited normally.
So the program is not interruppted when it reaches the breakpoint.

So what do I have to do in order to make debugging possible?
I think all this is related to the fact that the main 
progam /home/tmg/src/kde/build_debug/kdenetwork/kget/kget is only a script or 
a wrapper or whatever which calls the "real" application inside.

Thanks,
Thomas