From: Arnout E. <no...@bz...> - 2012-11-13 16:39:02
|
On Mon, Nov 12, 2012 at 12:06:02AM -0200, Silas Silva wrote: > I soon realized that time events were generated by SIGALRM. So there > could be anything related with signals. So, my investigations confirm > that a minor change is necessary to make it work. Just comment line 543 > of libmainloop/signal.c: > > sigaction(SIGCHLD, &sa, NULL); > > And it works like a charm, but I don't know if it breaks other things. > > I'm not a C programmer expert. So I'd like to ask you if you know why > it could be happening. If it works under GNU/Linux, it is probably > something regarding implementation of signals in NetBSD. > > Do you have any idea? > > Why SIGCHLD is being intercepted? I haven't looked *too* closely yet, but it seems this is used somehow in libmainloop. Looks like it is used to provide a 'mainloop_sigchld_hook' hook, but I don't see this hook actually being used anywhere. Anyone? Arnout |