Search Results for "fix"

Shadowsocks-libev is a lightweight secured SOCKS5 proxy for embedded devices and low-end boxes. Shadowsocks-libev is written in pure C and depends on libev. It's designed to be a lightweight implementation of shadowsocks protocol, in order to keep the resource usage as low as possible. Snap is the recommended way to install the latest binaries. You can build shadowsocks-libev and all its dependencies by script. The latest shadowsocks-libev has provided a redir mode. You can configure your...

For C (and CPP obviously): Include a fast and tiny RAM-tracing feature for Real-Time (RT) debugging purposes. >> ONLY FOR DEBUGGING << Very much faster than printf-debugging, which may result in unforseen results in an RT environement.

A cross-platform implementation of a mutex, that automatically checks for everything, you might be doing wrong: - DeadLocks - Invalid mutex leave order - Thread Shutdown, while still holding mutex locks - Destroying a locked mutex - (Un)Locking a destroyed mutex - UnLocking an unlocked mutex - UnLocking an mutex locked by another thread - Locking a non-recursive, locked mutex - Not destroying all mutexes before application termination Every abnormal produces a console output with file and line information about were it is located and why it happened. The main purpose of debug_mutex is the detection of deadlocks and outputting useful information, to fix it, by telling you exactly, where the recursion happened. Debug_mutex can easily be disabled and simply used as a cross-platform mutex Library Debug_mutex can be linked statically or externally