Difference between revisions of "Valgrind"

From Free Software Directory
Jump to: navigation, search
(Created page with "{{Entry |Name=Valgrind |Short description=Memory debugger |Full description=Valgrind finds memory-management problems by checking all reads and writes of memory are checked, and ...")
 
(New version)
Line 3: Line 3:
 
|Short description=Memory debugger
 
|Short description=Memory debugger
 
|Full description=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.
 
|Full description=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.
 +
|Homepage URL=http://valgrind.org/
 
|User level=none
 
|User level=none
|Status=Live
 
|Component programs=
 
|Homepage URL=http://valgrind.org/
 
|VCS checkout command=
 
 
|Computer languages=C
 
|Computer languages=C
 
|Documentation note=User manual available in HTML format from http://valgrind.org/docs/manual/manual.html
 
|Documentation note=User manual available in HTML format from http://valgrind.org/docs/manual/manual.html
|Paid support=
 
|IRC help=
 
|IRC general=
 
|IRC development=
 
 
|Related projects=Electric_Fence,MemCheck_Deluxe,halloc,Memtest86,KCachegrind
 
|Related projects=Electric_Fence,MemCheck_Deluxe,halloc,Memtest86,KCachegrind
 
|Keywords=development,programming,debugging,memory,valgrind,malloc
 
|Keywords=development,programming,debugging,memory,valgrind,malloc
|Is GNU=n
+
|Version identifier=3.12.0
|Last review by=Janet Casey
+
|Version date=2016/10/20
|Last review date=2005-05-11
+
|Version status=stable
 +
|Version download=http://valgrind.org/downloads/valgrind-3.12.0.tar.bz2
 +
|Version comment=3.12.0 stable released 2016-10-20
 +
|Last review by=Alejandroindependiente
 +
|Last review date=2017/01/08
 
|Submitted by=Database conversion
 
|Submitted by=Database conversion
 
|Submitted date=2011-04-01
 
|Submitted date=2011-04-01
|Version identifier=1.4.0
+
|Status=
|Version date=2005-03-24
+
|Is GNU=No
|Version status=stable
+
|License verified date=2002-07-03
|Version download=http://valgrind.org/downloads/valgrind-2.4.0.tar.bz2
+
}}
 +
{{Project license
 +
|License=GPLv2
 +
|License verified by=Janet Casey
 
|License verified date=2002-07-03
 
|License verified date=2002-07-03
|Version comment=1.4.0 stable released 2005-03-24
 
 
}}
 
}}
 
{{Person
 
{{Person
 +
|Real name=Julian Seward
 
|Role=Maintainer
 
|Role=Maintainer
|Real name=Julian Seward
 
 
|Email=jseward@acm.org
 
|Email=jseward@acm.org
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
 
{{Person
 
{{Person
 +
|Real name=Daniel Berlin
 
|Role=Contributor
 
|Role=Contributor
|Real name=Daniel Berlin
 
|Email=
 
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
 
{{Person
 
{{Person
 +
|Real name=Dirk Mueller
 
|Role=Contributor
 
|Role=Contributor
|Real name=Dirk Mueller
 
|Email=
 
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
 
{{Person
 
{{Person
 +
|Real name=Michael Matz
 
|Role=Contributor
 
|Role=Contributor
|Real name=Michael Matz
 
|Email=
 
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
 
{{Person
 
{{Person
 +
|Real name=Nicholas Nethercote
 
|Role=Contributor
 
|Role=Contributor
|Real name=Nicholas Nethercote
 
 
|Email=njn25@cam.ac.uk
 
|Email=njn25@cam.ac.uk
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
 
{{Person
 
{{Person
 +
|Real name=Simon Hausmann
 
|Role=Contributor
 
|Role=Contributor
|Real name=Simon Hausmann
 
|Email=
 
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
Line 88: Line 83:
 
|Software-development=debugging
 
|Software-development=debugging
 
|Use=software-development
 
|Use=software-development
}}
 
{{Project license
 
|License=GPLv2
 
|License verified by=Janet Casey
 
|License verified date=2002-07-03
 
 
}}
 
}}
 
{{Software prerequisite
 
{{Software prerequisite
Line 98: Line 88:
 
|Prerequisite description=gdb
 
|Prerequisite description=gdb
 
}}
 
}}
 +
{{Featured}}

Revision as of 19:36, 7 January 2017


[edit]

Valgrind

http://valgrind.org/
Memory debugger

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.





Licensing

License

Verified by

Verified on

Notes

License

GPLv2

Verified by

Janet Casey

Verified on

3 July 2002




Leaders and contributors

Contact(s)Role
Nicholas Nethercote Contributor
Julian Seward Maintainer
Michael Matz Contributor
Daniel Berlin Contributor
Dirk Mueller Contributor
Simon Hausmann Contributor


Resources and communication

AudienceResource typeURI
Debian (Ref)https://tracker.debian.org/pkg/valgrind
DeveloperMailing List Info/Archivehttp://lists.sourceforge.net/mailman/listinfo/valgrind-developers
Bug TrackingE-mailmailto:jseward@acm.org
SupportMailing List Info/Archivehttp://lists.sourceforge.net/mailman/listinfo/valgrind-users
HelpMailing List Info/Archivehttp://lists.sourceforge.net/mailman/listinfo/valgrind-announce


Software prerequisites

KindDescription
Weak prerequisitegdb




Entry









































Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.

The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.