On 2 September 2015 at 05:33, Jim Charlton wrote:
Hi Jim,
> I have had similar problems and ended up using g_spawn_async_with_pipes()
> with a separate binary. This works well for me as I often need to launch
> several instances of this "thread".
g_spawn_async_* have the
Hi all:
I'm working on a project which, for several reasons, will use the Posix
fork() call. The question is: if I have an active GTK main loop in the
program before calling fork(), is there something I have to do after
calling it in the child process? I know that I must NOT use Gtk calls in
the
On 15-09-01 07:27 AM, rastersoft wrote:
In fact, I'm already using pipes and more; I can just replace the Thread
call with a fork() and everything will work fine. The only idea I see I
can use is to physically separate both process in different binaries and
use named pipes...
On 01/09/15 16:05,
In fact, I'm already using pipes and more; I can just replace the Thread
call with a fork() and everything will work fine. The only idea I see I
can use is to physically separate both process in different binaries and
use named pipes...
On 01/09/15 16:05, Chris Vine wrote:
> On Tue, 1 Sep 2015
Thanks for your answer. Unfortunately, I'm running out of options:
currently I'm using threads, but there is a nasty bug that makes my
program crash sometimes. It is very subtle, because it hapens usually
after being running for two-three days. It is a double free. I tried
with Valgrind, but when
On Tue, 1 Sep 2015 15:33:19 +0200
rastersoft wrote:
> Thanks for your answer. Unfortunately, I'm running out of options:
> currently I'm using threads, but there is a nasty bug that makes my
> program crash sometimes. It is very subtle, because it hapens usually
> after
On Tue, Sep 1, 2015 at 10:33 AM, rastersoft wrote:
> It is very subtle, because it hapens usually
> after being running for two-three days. It is a double free. I tried
> with Valgrind, but when I use it, the error doesn't trigger, which makes
> me suspect it is a race