| Projects on Google Code | Results 1 - 7 of 7 |
This project is about detecting data races (race conditions).
If you are interested in this subject, start browsing wiki pages:
* ThreadSanitizer -- a data race detector.
* DynamicAnnotations -- a race detector API
* RacecheckUnittest -- the set of unit tests.
* RaceCheckerClass -- ...
valgrind,
debugging,
multithreading,
test,
testing,
unittest,
datarace,
thread,
pthread,
threads,
multithreaded,
helgrind
Using the malloc library hooks __malloc_hook and __free_hook, jmem gathers information about allocations and deallocations. Unlike valgrind and others, jmem will provide a backtrace for both the allocation and deallocation.
To use, include "jmem.h" and recompile.
Chronicle records every memory and register write in the execution of a Linux process, using Valgrind to instrument execution at the machine code and system call level. These events are indexed and compressed; from the resulting database the Chronicle query tool can efficiently reconstruct the state...
Flayer is a Valgrind tool which provides bit-precise dynamic taint analysis of input to a target application. In addition, it allows this flow to be altered irrespective of content through the modification of conditional jump (if clauses) and function call behavior.
In addition, a small, Python ...
This is a Google Summer of Code project (2009), supported by GEGL/GIMP.
It is a program that will store Valgrind, or more precisely callgrind/cachegrind data in a database, present it for performance analysis as well as analysis of performance trend over time.
These are the sources of my Code Profiling HOWTO.
Callspector helps developers to compare callgrinds generated files.