Difference between revisions of "Checker"
(Created page with "{{Entry |Name=checker |Short description=Finds memory errors at runtime |Full description='checker' can help find bugs that standard tools cannot always find. The best example is...") |
(* "The GNU 'checker' package has been decommissioned, as 'valgrind' does a better job and is being actively maintained.") |
||
| Line 2: | Line 2: | ||
|Name=checker | |Name=checker | ||
|Short description=Finds memory errors at runtime | |Short description=Finds memory errors at runtime | ||
| − | |Full description='checker' can help find bugs that standard tools cannot always find. The best example is memory leaks. A memory leak is a zone of memory, allocated with malloc that is not used anymore. So the memory allocated is lost. This means you program needs more memory and runs slower, since your OS might have to start swapping. It detects bad memory accesses such as: reading uninitialized memory, writing in a freed zone, writing or reading outside of a memory block, and using NULL pointers. This is particularly useful for big programs with many functions. Checker maintains bitmaps to keep track of the status of each byte of memory. The status can be writable, readable, both, or none. When memory is allocated, the new memory becomes write-only: you are not allowed to read it because it has not been initialized. But when you you write to this new block, those bytes become readable and writable. When the block is freed, the bytes become unreadable and unwritable. Red zones are unreadable and unwritable memory, so that each access to a red zone produces a warning. This project was a GNU package. It has since been decommissioned and is no longer developed. | + | |Full description=* "The GNU checker package has been decommissioned, as valgrind does a better job and is being actively maintained." |
| + | |||
| + | 'checker' can help find bugs that standard tools cannot always find. The best example is memory leaks. A memory leak is a zone of memory, allocated with malloc that is not used anymore. So the memory allocated is lost. This means you program needs more memory and runs slower, since your OS might have to start swapping. It detects bad memory accesses such as: reading uninitialized memory, writing in a freed zone, writing or reading outside of a memory block, and using NULL pointers. This is particularly useful for big programs with many functions. Checker maintains bitmaps to keep track of the status of each byte of memory. The status can be writable, readable, both, or none. When memory is allocated, the new memory becomes write-only: you are not allowed to read it because it has not been initialized. But when you you write to this new block, those bytes become readable and writable. When the block is freed, the bytes become unreadable and unwritable. Red zones are unreadable and unwritable memory, so that each access to a red zone produces a warning. This project was a GNU package. It has since been decommissioned and is no longer developed. | ||
| + | |Homepage URL=http://www.gnu.org/software/checker/ | ||
|User level=none | |User level=none | ||
| − | |||
|Component programs=checkergcc | |Component programs=checkergcc | ||
| − | |||
| − | |||
|Computer languages=C | |Computer languages=C | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Related projects=halloc,Memtest86,Memwatch | |Related projects=halloc,Memtest86,Memwatch | ||
|Keywords=memory,malloc,checker,runtime,memory leak,checking,errors | |Keywords=memory,malloc,checker,runtime,memory leak,checking,errors | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Version identifier=0.9.9.1 | |Version identifier=0.9.9.1 | ||
|Version date=2002-08-24 | |Version date=2002-08-24 | ||
|Version status=stable | |Version status=stable | ||
| − | |Version download= | + | |Version download=ftp://alpha.gnu.org/gnu/checker/Checker-0.9.9.1.tar.gz |
| + | |Version comment=0.9.9.1 stable released 2002-08-24 | ||
| + | |Last review by=Alejandroindependiente | ||
| + | |Last review date=2017/01/28 | ||
| + | |Submitted by=Database conversion | ||
| + | |Submitted date=2011-04-01 | ||
| + | |Status= | ||
| + | |Is GNU=Yes | ||
| + | |GNU package identifier=checker | ||
| + | |License verified date=2001-03-01 | ||
| + | }} | ||
| + | {{Project license | ||
| + | |License=GPLv2 | ||
| + | |License verified by=Janet Casey | ||
|License verified date=2001-03-01 | |License verified date=2001-03-01 | ||
| − | |||
}} | }} | ||
{{Person | {{Person | ||
| + | |Real name=Ben Pfaff | ||
|Role=Maintainer | |Role=Maintainer | ||
| − | |||
| − | |||
|Resource URL= | |Resource URL= | ||
}} | }} | ||
{{Person | {{Person | ||
| + | |Real name=Ben Pfaff | ||
|Role=Contributor | |Role=Contributor | ||
| − | |||
| − | |||
|Resource URL= | |Resource URL= | ||
}} | }} | ||
| Line 43: | Line 43: | ||
|Software-development=debugging | |Software-development=debugging | ||
|Use=software-development | |Use=software-development | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{Software prerequisite | {{Software prerequisite | ||
| Line 57: | Line 52: | ||
|Prerequisite description=gcc | |Prerequisite description=gcc | ||
}} | }} | ||
| + | {{Featured}} | ||
Revision as of 18:17, 28 January 2017
GNU Checker
https://www.gnu.org/software/checker/
Finds memory errors at runtime.
Checker is a debugging tool suite which is used to find memory errors at runtime.
'Checker' can help find bugs that standard tools cannot always find. The best example is memory leaks. A memory leak is a zone of memory, allocated with malloc that is not used anymore. So the memory allocated is lost. This means you program needs more memory and runs slower, since your OS might have to start swapping. It detects bad memory accesses such as: reading uninitialized memory, writing in a freed zone, writing or reading outside of a memory block, and using NULL pointers. This is particularly useful for big programs with many functions. Checker maintains bitmaps to keep track of the status of each byte of memory. The status can be writable, readable, both, or none. When memory is allocated, the new memory becomes write-only: you are not allowed to read it because it has not been initialized. But when you you write to this new block, those bytes become readable and writable. When the block is freed, the bytes become unreadable and unwritable. Red zones are unreadable and unwritable memory, so that each access to a red zone produces a warning.
Licensing
License
Verified by
Verified on
Notes
Leaders and contributors
Resources and communication
| Audience | Resource type | URI |
|---|---|---|
| Savannah (Ref) | https://savannah.nongnu.org/projects/checker/ | |
| General | https://savannah.gnu.org/people/ | |
| Mailing List | https://lists.gnu.org/mailman/listinfo/gnu-system-discuss/ | |
| VCS Repository Webview | https://cvs.savannah.nongnu.org/viewvc/checker/ | |
| Download | https://alpha.gnu.org/gnu/checker/ |
Software prerequisites
| Kind | Description |
|---|---|
| Source requirement | GCC 2.8.1 |
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.