[8 total ]
Valgrind is an award-winning suite of tools for debugging and profiling Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making
... [More]
your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs.
The Valgrind distribution currently includes four tools: a memory error detector, a cache (time) profiler, a call-graph profiler, and a heap (space) profiler. [Less]
KCachegrind is a KDE viewer of profiling data generated by Callgrind.
iogrind is a prototype I/O profiling tool, under development. It aims to give a fairly accurate picture of all the I/O your application would perform on a cold start: this can help to accelerate your application's cold start performance. It also has a nice file-system view.
Software library to ease development in the C programming language.
Perl extension to test Perl code with valgrind.
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
... [More]
function call behavior.
In addition, a small, Python wrapper library, LibFlayer, is included. It provides an easy interface for automation.
This is a proof of concept implementation, but it is fully functional. Please check it out! [Less]
This project aims to create a test suite for helgrind (a data race detection tool, part of valgrind, http://www.valgrind.org) and potentially any other data race detector.
Hopefully, everything really useful from this project will eventually be
... [More]
merged into the 'official' helgrind.
If you are interested in this project, start browsing wiki pages RacecheckUnittest -- the set of unit tests. MemoryStateMachines -- general discussion of memory state machines (core logic of any race detector) MSMHelgrind -- The state machine in helgrind 3.3.0 MSMHelgrind340 -- The state machine in HGDEV branch and maybe in helgrind 3.4.0 UnderstandingHelgrindReports -- How to understand races reports by helgrind with MSMHelgrind340 state machine. RaceCheckerClass -- A handy utility to check if there is indeed a race. HelgrindAndVim -- How to analyze helgrind logs using Vim. [Less]
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
... [More]
Chronicle query tool can efficiently reconstruct the state of memory and/or registers at any point during the execution. Additional queries such as "when was the last write to location X before time T" and "when was location X executed between times T1 and T2" are also supported. This infrastructure has a variety of possible uses, but the most obvious use is as the basis for powerful debuggers.
Chronicle by itself is not all that useful to anyone except tool builders. If you're looking for a useful debugger, try Chronomancer, an Eclipse-based UI for debugging C and C++ programs using Chronicle.
Chronicle is released with the permission of Novell. Thanks Novell! [Less]