Categories
Audio
Business and productivity
Database
Education
Email
Games
Graphics
Hobbies
Interface
Internet applications
Live communications
Localization
Mathematics
Printing
Science
Security
Software development
Software libraries
System administration
Text creation and manipulation
Video
Web authoring
Valgrind
Valgrind finds memory-management problems by checking all reads and writes of memory are checked, and intercepting all calls to malloc/new/free/delete. As a result, Valgrind can detect problems like the use of uninitialised memory, reading/writing memory after it has been free'd, reading/writing off the end of malloc'd blocks, reading/writing inappropriate areas on the stack, memory leaks, and passing of uninitialised and/or unaddressible memory to system calls.
Valgrind tracks each byte of memory with nine status bits: one tracks addressibility, and the other eight validity. As a result, it can detect the use of single uninitialised bits, and does not report spurious errors on bitfield operations. Valgrind debugs almost any dynamically-linked ELF x86 executable without modification or recompilation.
Last updated 11 May, 2005
About
Leadership
- Julian Seward - Maintainer
- Nicholas Nethercote - Contributor
- Daniel Berlin - Contributor
- Michael Matz - Contributor
- Simon Hausmann - Contributor
- Dirk Mueller - Contributor
Requirements
- gdb (Weak Prerequisite)
Related Projects
Electric Fence, KCachegrind, MemCheck Deluxe, Memtest86, halloc
Versions
1.4.0
1.4.0 stable released 2005-03-24
- Released: 24 Mar, 2005
- Code Maturity: Stable
- Source Archive: http://valgrind.org/downloads/valgrind-2.4.0.ta...
- Licenses: GPLv2
- Interfaces: Command Line
User Community and Support
User manual available in HTML format from http://valgrind.org/docs/manual/manual.html