evutil_time: improve evutil_gettimeofday on Windows

If present, use GetSystemTimePreciseAsFileTime instead of
GetSystemTimeAsFileTime. Available since Windows 8.

(cherry picked from commit f0b3160f

evutil_time: improve evutil_gettimeofday on Windows

If present, use GetSystemTimePreciseAsFileTime instead of
GetSystemTimeAsFileTime. Available since Windows 8.

(cherry picked from commit f0b3160f8ce7fbd411493dcd023f562f4f9d17ee)

show more ...

evutil_time: Implements usleep() using wait funtion on Windows

(cherry picked from commit 6412f34f242e9b5b87f0378715baf97ba0bf1a8c)

evutil_time: detect and use _gmtime64_s()/_gmtime64()

(cherry picked from commit 148d12ad31b03a813f4ffd9df14a85392aa74130)

Replace all EVENT_HAVE with EVENT__HAVE (EVENT__HAVE_USLEEP)

(cherry picked from commit 35258a1f4e09d9e7fcb003cd0572343670180495)

Avoid possible SEGVs in select() (in unit tests)

Per the POSIX definition of select():

http://pubs.opengroup.org/onlinepubs/009696699/functions/pselect.html

"Upon successful completion, the select

Avoid possible SEGVs in select() (in unit tests)

Per the POSIX definition of select():

http://pubs.opengroup.org/onlinepubs/009696699/functions/pselect.html

"Upon successful completion, the select() function may modify the object
pointed to by the timout argument."

If "struct timeval" pointer is a "static const", it could potentially
be allocated in a RO text segment. The kernel would then try to copy
back the modified value (with the time remaining) into a read-only
address and SEGV.

Signed-off-by: Philip Prindeville <[email protected]>
Closes: #614
(cherry picked from commit 33baa4e59fbf9432d77a19c6b2b45402580b79a5)

show more ...

test: fix util/date_rfc1123 under win32

Refs: #417
v2: check when gmtime() returns NULL
v3: fix overflow cases

Fix UB in evutil_date_rfc1123()

As pointed in https://github.com/libevent/libevent/pull/417#issuecomment-267860738
"code is unsafe because in evutil_date_rfc1123() the pointer to the
automatic v

Fix UB in evutil_date_rfc1123()

As pointed in https://github.com/libevent/libevent/pull/417#issuecomment-267860738
"code is unsafe because in evutil_date_rfc1123() the pointer to the
automatic variable struct tm cur is used outside the scope it defined."

Checked with `clang -fsanitize=address -fsanitize-address-use-after-scope`
and test that call evutil_date_rfc1123() with tm==NULL

show more ...

http: do not use local settings for Date header

evutil_time: include <unistd.h> when there is only sleep()/usleep()

Implement new/free for struct evutil_monotonic_timer and export monotonic time functions

Check CLOCK_MONOTONIC_* at runtime if needed.

(We need this to avoid compile errors on cygwin. Fixes github issue
75.)

Add regress_finalize to makefile.nmake

Avoid unused-var warning on systems with clock_gettime but without CLOCK_MONOTONIC_COARSE

Simple unit tests for monotonic timers

Implement fast/precise monotonic clocks on Windows

This uses code from libutp, which was released under the MIT
license; see evutil_time.c and LICENSE changes.

Refactor monotonic timer handling into a new type and set of functions; add a gettimeofday-based ratcheting implementation

Now, event.c can always assume that we have a monotonic timer; this
makes e

Refactor monotonic timer handling into a new type and set of functions; add a gettimeofday-based ratcheting implementation

Now, event.c can always assume that we have a monotonic timer; this
makes event.c easier to write.

show more ...

Split out time-related prototypes into time-internal.h

Split out time-related evutil functions into a new evutil_time.c