KDE4 KProcess status

[Thiago Macieira]

Andreas Pakulat wrote:
>Well, somehow QProcess doesn't get the SIGCHLD after being started in a
>gdb process that itself was started in KProcess.

Do I understand correctly that starting a process with KProcess makes it 
(after exec(2) !) not work with QProcess?

QProcess sets the signal handler but it uses an atomic integer to make 
sure it does so only once. I don't see how a pre-exec() action can 
interfere with the post-exec() status of that integer.

>As I said before I have no real clue how that can happen, all I know is
>that it does happen.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070311/e90ecf92/attachment.sig>