kc3-lang/libevent/event.c
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
2bfda401 | 2012-04-30 17:30:48 | If a higher-priority event becomes active, don't continue running events of the current priority. Bug found by Ralph Castain. | |
|
dfd808cb | 2012-04-19 00:25:12 | If time has jumped so we'd reschedule a periodic event in the past, schedule it for the future instead Fixes an issue reported on libevent-users in the thread "a dead looping bug when changing system time backward". Previously, if time jumped forward 1 hour[*] and we had a one-second periodic timer event, that event would get invoked 3600 times. That's almost certainly not what anybody wants. In a future version of Libevent, we should expose the amount of time that the callbac kwould have been invoked somehow. [*] Forward time jumps can happen with nonmonotonic clocks, or with clocks that jump on suspend/resume. It can also happen from Libevent's point of view if the user exits from event_base_loop() and doesn't call it again for a while. | |
|
bec22b41 | 2012-04-19 18:15:12 | Refactor event_persist_closure: raise and extract some common logic | |
|
e49e2891 | 2012-02-10 17:29:53 | Update copyright notices to 2012 | |
|
3f18ad1b | 2012-01-23 18:15:44 | Fix a fd leak in event_reinit() We were supposed to be closing the ev_signal_pair sockets. | |
|
6e41cdc1 | 2012-01-23 17:59:16 | Fix a list corruption bug when using event_reinit() with signals present While re-adding all the events, event_reinit() could add a signal event, which could then cause evsig_add() to add the base->sig.ev_signal event. Later on its merry path through base->eventqueue, event_reinit() would find that same event and give it to event_io_add a second time. This would make the ev_io_next list for that fd become circular. Ouch! | |
|
27737d55 | 2012-01-21 12:55:15 | Add function to check referential integrity of an event_base | |
|
f0325167 | 2012-01-09 11:33:38 | Remove bogus casts of socket to int before calling ev_callback This should make 64-bit windows act better. Found by Mark Heily. | |
|
11f36a5f | 2011-12-05 15:02:27 | Be absolutely sure to clear pncalls before leaving event_signal_closure I thought we'd fixed the cases where this could come up, but apparently having an event_base_break() happen while processing signal events could get us in trouble. Found by Remi Gacogne. Sourceforge issue 3451433 . | |
|
e7874133 | 2011-11-14 17:33:02 | Don't try to make notifiable event_base when no threading fns are configured |