Search Results for "fix"

...The same execution is replayed every time. rr also provides efficient reverse execution under gdb. Set breakpoints and data watchpoints and quickly reverse-execute to where they were hit. rr works on real applications and is used by many developers to fix real bugs. It makes debugging hard bugs much easier, but also speeds up debugging of easy bugs.

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