Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

[Al Thomas <astavale yahoo co uk>]

  > On Thursday, 14 March 2019, 05:59:16 GMT, Wolfgang Mauer <wolfgang mauer kabelmail de> wrote: > So please 
give me a hand.. Is this a vala or GLib problem?
> > As far as the bug goes it 
> is:https://gitlab.gnome.org/GNOME/vala/issues/664 > https://gitlab.gnome.org/GNOME/glib/issues/1512

Looking over the report again I think the callback from g_child_watch_add () wasn'tbeing called so the 
process exited by the output kept being piped in. That's why itwas null.
Given the GLib API is a higher level API to abstract away platform implementationsthen the first place to 
look is GLib. I have made a quick note onhttps://gitlab.gnome.org/GNOME/glib/issues/1512that this is 
occurring on both Windows and macOS.
One thing you could try is to find an alternative way of tidying up after the output hasfinished. The GLib 
documentation for g_spawn_async_with_pipes () ( 
https://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#g-spawn-async-with-pipes )is detailed, 
with notes on cross platform support.
So the answer to your question is neither. The problem needs further investigation beforethe direct cause can 
be identified and fixed.