Searched refs:signals (Results 1 – 3 of 3) sorted by relevance
2375 static ANSIG signals [EV_NSIG - 1]; variable2518 if (expect_false (signals [i].pending)) in pipecb()2549 EV_A = signals [signum - 1].loop; in ev_feed_signal()2555 signals [signum - 1].pending = 1; in ev_feed_signal()2583 if (expect_false (signals [signum].loop != EV_A)) in ev_feed_signal_event()2587 signals [signum].pending = 0; in ev_feed_signal_event()2590 for (w = signals [signum].head; w; w = w->next) in ev_feed_signal_event()4044 !signals [w->signum - 1].loop || signals [w->signum - 1].loop == loop)); in ev_signal_start()4046 signals [w->signum - 1].loop = EV_A; in ev_signal_start()4128 if (!signals [w->signum - 1].head) in ev_signal_stop()[all …]
116 (C<ev_periodic>), synchronous signals (C<ev_signal>), process status319 in the presence of threads. For example, you could block signals455 unblocking the signals.2431 interrupted by signals you can block all signals in an C<ev_check> watcher2445 certain signals to be blocked.2468 threads in a process block signals, which is hard to achieve.2475 these signals. You can pass on any signals that libev might be interested3946 base that registered the signal gets the signals.4827 signals): Normally, libev tries to deduce the maximum number of signals5326 The most portable way to handle signals is to block signals in all threads[all …]
9 TODO: document the special problem of signals around fork.87 - try to detect signals around a fork faster (test program by108 caused signals to not be handled anymore.279 - actually 0-initialise struct sigaction when installing signals.332 - assume negative return values != -1 signals success of port_getn