Re: async, watches and blocking/unblocking

2005-04-06 Thread Ole C.
Hi, I fixed it. I did numerous things, but in the end (I am not entirely certain if this was all I did though) it seems that (atleast part of) the problem was due to using a fixed buffer size for the read/write channel operations in the callbacks. When I started dynamically allocating the buffer b

Re: async, watches and blocking/unblocking

2005-04-06 Thread Santhosh
Hi, Why don't you include the code... probably a part of it... Make sure you are not deadlocking (reading a pipe at both ends..) -- Santhosh. ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ Project - http://eccvs.sf.net ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ ___ gtk-app-devel

async, watches and blocking/unblocking

2005-04-05 Thread Ole C.
Hello list, I spawn 2 programs with g_spawn_async_with_pipes. stdout on the first goes to stdin on the second. stdout on the second is written to file. I use g_io_channel_unix_new to create the channels for the stdins and stdouts. I use g_io_add_watch to setup calls to the callback functions (one