A fellow KDevelop hacker has reported that when running kdevelop itself
under CVS HEAD of gdb, kdevelop hangs. What happens if that kdevelop spawns
subprocess, and then does not notice it has exited, because it never
receives SIGCHLD. I attach a much reduced project that requires only Qt4,
and probably an even more reduced project is possible.

If I apply the attached patch to GDB, things work fine -- but I suspect
this 'fix' will break something else. 

Pedro, I think this SIGCHLD magic is your doing -- do you have any ideas
how to fix it? 

Thanks,
Volodya