KJAS or KProcess bug?

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 15 September 2003 23:48, David Faure wrote:
> http://www.seq.qc.ca/accueil_fr.htm
> After KJAS exits, KProcess thinks it keeps sending empty data, for a reason
> I can't explain.....
>
> 28532 kjas: ERROR: could not parse length out of:
> 28532 kjas: ERROR: could not parse length out of:
> 28532 kjas: ERROR: could not parse length out of:
> 28532 kjas: ERROR: could not parse length out of:
> 28532 kjas: ERROR: could not parse length out of:
> 28532 kjas: ERROR: could not parse length out of:
> [... you get the idea ...]
>
> gdb only says that the select() in KProcess::commClose() keeps saying
> that fd 32 (which is out[0]) has data...

Typical for a situation in which the fd got closed. What's strange is that
KProcess doesn't detect that the fd got closed. Are you using KProcess with 
the NoRead option? Are you setting "len" accordingly (to 0) when this 
situation happens?

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/ZsBgN4pvrENfboIRAtVwAKCWMrj/yAuBvf34hTYko7gulsEyvwCeOJVY
9D1ZkFwsoN8NBxh8QzRepoc=
=YGFY
-----END PGP SIGNATURE-----