kdevelop (4.7) launching background *processes*?

[Kevin Funk]

On Thursday 11 December 2014 15:48:07 René J.V. Bertin wrote:
> On Thursday December 11 2014, Milian Wolff wrote regarding "Re: kdevelop
> (4.7) launching background *processes*?"
> 
> 
> In the end I rebuilt Qt with QT_PROCESS_DEBUG (I was already rebuilding it
> anyway) and a modification to output the PID too, and found the culprit. I
> already had a hunch that the zombie issue had to do with the fact that I'm
> working to move MacPorts' qt4-mac into its own install tree (so we can have
> qt5-mac at the same time), and indeed it is. The zombies are created by
> kdevelop trying to execute qmake with the hardcoded path of where it used
> to live. Since I'm taking care that my moved Qt4 install is still
> accessible to non-rebuilt clients through a set of symlinks, I had not
> rebuilt kdevelop.
> 
> So the question now becomes:
> - How is the hardcoded (default) qmake path determined?

In a perfect world, we should have a "Kits" settings page like QtCreator has, 
for setting up different Qt versions.

Right now we're just checking $PATH.

> - Will kdevelop require me to install qtchooser or similar?
> - Why does one get a zombie after trying to launch a non-existent
> executable? Qt4 uses qprocess_unix.cpp on OS X, but I don't get a zombie
> when I remove /usr/bin/qmake on my Linux box.

I remember this issue.

There's a Qt bug for this already (pretty old):
  https://bugreports.qt-project.org/browse/QTBUG-27945

=> Low priority apparently.

> Sorry for the noise,
> René

-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org