kc3-lang/libevent/test
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
e06206eb | 2012-05-03 12:15:11 | Oops; fix the *right* windows compile issue | |
|
be7a0be8 | 2012-05-03 12:05:52 | Fix win32 build issues: sleep, pid_t | |
|
30f06715 | 2012-04-30 21:45:43 | Merge remote-tracking branch 'github/20_active_prio_inv' into patches-2.0 | |
|
b3887cdf | 2012-04-11 21:33:27 | Work-around a stupid gcov-breaking bug in OSX 10.6 This only affects the unit tests. Fix found at http://rachelbythebay.com/w/2011/07/12/forkcrash/ (Backport from 2.1) | |
|
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. | |
 |
2d67b638 | 2012-02-14 15:37:58 | Changed OPENSSL_LDFLAGS to OPENSSL_LIBADD | |
|
92781968 | 2012-02-14 15:01:02 | Added OPENSSL_LDFLAGS env variable which is appended to SSL checks. If openssl is not installed system-wide or not compiled as a shared library, some systems require various link flags (e.g., -ld). | |
|
e49e2891 | 2012-02-10 17:29:53 | Update copyright notices to 2012 | |
|
9f9e259f | 2012-01-26 15:04:24 | Better workaround for Linux 3.2 edge-triggered epoll bug On further investigation, it appears that this problem is limited to AF_UNIX sockets, so let's just do the test on AF_INET sockets. |