Searched refs:warn_on_full_buffer (Results 1 – 5 of 5) sorted by relevance
117 int warn_on_full_buffer; member119 } wakeup = {.fd = INVALID_FD, .warn_on_full_buffer = 1, .use_send = 0};124 int warn_on_full_buffer; member125 } wakeup = {.fd = INVALID_FD, .warn_on_full_buffer = 1};292 if (wakeup.warn_on_full_buffer || in trip_signal()311 if (wakeup.warn_on_full_buffer || in trip_signal()677 int warn_on_full_buffer = 1; in signal_set_wakeup_fd() local687 &fdobj, &warn_on_full_buffer)) in signal_set_wakeup_fd()697 &fd, &warn_on_full_buffer)) in signal_set_wakeup_fd()751 wakeup.warn_on_full_buffer = warn_on_full_buffer; in signal_set_wakeup_fd()[all …]
457 .. function:: set_wakeup_fd(fd, *, warn_on_full_buffer=True)485 ``warn_on_full_buffer=True``, which will at least cause a warning492 you should set ``warn_on_full_buffer=False``, so that your users499 Added ``warn_on_full_buffer`` parameter.
548 New argument warn_on_full_buffer to signal.set_wakeup_fd lets you control
1264 The new *warn_on_full_buffer* argument to the :func:`signal.set_wakeup_fd`
1903 …dule.c - wakeup variable static volatile struct { SOCKET_T fd; int warn_on_full_buffer; int use_se…