KDE4 KProcess status

[Andreas Pakulat]

On 11.03.07 18:14:36, Andreas Pakulat wrote:
> On 11.03.07 15:27:09, Thiago Macieira wrote:
> > Andreas Pakulat wrote:
> > >So the only real problem for me that is left is if KProcess really gets
> > >ditched. Because currently Qt4 QProcess doesn't work when debugging the
> > >app inside KDevelop3 due to unix-signal-problems (I think) with KDE3
> > >KProcess. What I see there is that the Qt4 QProcess never sends out any
> > >of its signals. This works fine when only running the app or when using
> > >plain gdb and our debugger doesn't do any unix-signal handling itself.
> > >I'm probably going to bug TT with that though, maybe they can sort that
> > >out somehow...
> > 
> > QProcess does not require Unix signals to work. It does require the 
> > SIGCHLD signal to be notified of child processes terminating. But that 
> > doesn't affect reading and writing.
> > 
> > It changes SIGHUP and SIGPIPE a bit, but it shouldn't influence the 
> > outcome. Those are only used in detached processes.
> 
> Well, somehow QProcess doesn't get the SIGCHLD after being started in a
> gdb process that itself was started in KProcess. 
> 
> As I said before I have no real clue how that can happen, all I know is
> that it does happen.

Weird, a small Qt-only test application works fine in KDevelop debugger
:(

So there must be something different causing the problems when debugging
KDevelop4 inside KDevelop3...

Andreas

-- 
Live in a world of your own, but always welcome visitors.