KDE-Forum.org

Hi there !

I need to launch an application from within my application. Since I also need to be informed, when the child process exits (ie crashes etc.) I want to use the KProcess class.
It works perfectly as long as I am not starting it in debugging mode from within KDevelop. When I want to debug my application, then it just won't start the child process. I have found some statements on the internet, saying, that this is a known Problem, but I haven't found a solution to it yet.
You can try it very simply in your own application. Just add the following lines somewhere in your code (plus #include <kprocess.h> of course). When you start your application from commandline it launches kwrite. In debugging mode it won't.

Quoted

KProcess procTest;
procTest << "kwrite";
procTest.start(KProcess::DontCare);

I would appreciate some tips how to avoid this problem, since I really need to debug my code :-)

SmartyHias

Well, I also checked this. It doesn't matter if I instantiate the object by "new" or just as a local instance. Especially if I am starting the process with "KProcess:ontCare".
Besides it works perfectly fine when staring the application from shell. It just seizes to work when starting it with gdb. KDE-gdb or ddd-gdb doesn't make a difference.
You can try it yourself real quick, if you want. Just make a new project using a simple KDE-Application (Hello world or so). insert the 3 lines in the c-tor of your KMainWindow derived class. (it also doesn't matter if you put it into the c-tor or eg. a slot :-) ). build it and run it from a shell first and then using gdb.
Funny, but nasty little bug :-)

Have a nice evening

SmartyHias