Key | Value |
---|---|
FileName | ./usr/share/doc/packages/valgrind/html/manual-core.html |
FileSize | 173833 |
MD5 | 0FDF80736CF52EB352C62ED15B918B0A |
SHA-1 | 10D87816EADD391F7924052B1BC05B83CEF2D6FD |
SHA-256 | 2FDC45237CB5DD9E4A6D33C8EB713EFAD4687083B81A3CE17FD57C42C18FBDCC |
SSDEEP | 3072:Dg//zPPh+ug1Laqp4PI/LavKwNxiHZAIYCJz4A1hihz:D0Pu1Laqp4PI/LavKwNxiH6g9kh |
TLSH | T1EA04E823EA801373019382D9699923B9B7AFD13ED37159943DFDC32C5B02DA1827F59A |
hashlookup:parent-total | 6 |
hashlookup:trust | 80 |
The searched file hash is included in 6 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | BD938A16A3F17852089DEDCAAD925311 |
PackageArch | armv7hl |
PackageDescription | When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * 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 -- where pointers to malloc'd blocks are lost forever * Passing of uninitialised and/or unaddressable memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
PackageMaintainer | tv <tv> |
PackageName | valgrind |
PackageRelease | 1.mga9 |
PackageVersion | 3.20.0 |
SHA-1 | 2B8EBD461ABC4817A0AB0885F56B71CBF649BF28 |
SHA-256 | 2BCFE735E9B09296331C0D6AE5DEE0ECC65F1A7DC33F05375024392E7A8C973D |
Key | Value |
---|---|
MD5 | 34B014F9D42940A56F9B56DEC825BA60 |
PackageArch | i586 |
PackageDescription | When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * 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 -- where pointers to malloc'd blocks are lost forever * Passing of uninitialised and/or unaddressable memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
PackageMaintainer | tv <tv> |
PackageName | valgrind |
PackageRelease | 1.mga9 |
PackageVersion | 3.20.0 |
SHA-1 | 21FE14D9524CCCE98AACDA9E490FD34E3A3BFCD9 |
SHA-256 | 3FCC218E53B32A523DF3B3E378AA4A1B8685129C9BD91A92AEDBFA681680CC89 |
Key | Value |
---|---|
MD5 | 7F099E4A01DB20A61008E030A9CFBA8D |
PackageArch | s390x |
PackageDescription | Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications. |
PackageMaintainer | https://www.suse.com/ |
PackageName | valgrind |
PackageRelease | 150500.2.1 |
PackageVersion | 3.20.0 |
SHA-1 | E8DE8A1564ADC02DBB66DC438C6054ED64D00ED7 |
SHA-256 | AA75D88B58630D73CF9CD56B17670555D2B77BD3B03125C84EA2F6F63D1852CE |
Key | Value |
---|---|
MD5 | 4B878B8B2B26A3129F77C89F07BF31D8 |
PackageArch | x86_64 |
PackageDescription | Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications. |
PackageMaintainer | https://www.suse.com/ |
PackageName | valgrind |
PackageRelease | 150500.2.1 |
PackageVersion | 3.20.0 |
SHA-1 | 0F2655532BE9856A1E43959F360EB83D722B860F |
SHA-256 | FB690DF331F4FC4892E9437C3405D047452C18ACCA48F708A6239C3E63C5E53C |
Key | Value |
---|---|
MD5 | 49B03C279E46D9B69CD5559BD9B63971 |
PackageArch | x86_64 |
PackageDescription | When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * 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 -- where pointers to malloc'd blocks are lost forever * Passing of uninitialised and/or unaddressable memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
PackageMaintainer | tv <tv> |
PackageName | valgrind |
PackageRelease | 1.mga9 |
PackageVersion | 3.20.0 |
SHA-1 | 9514B0C8FFEDEFFC445084A9A2B559CE74C514A4 |
SHA-256 | 5DF8930B386FCD301BC9216C062BB11802E7ECDBEBDE515C6AC6ED040D3BD0A6 |
Key | Value |
---|---|
MD5 | CA243DC1241F7666EEE2DB4CD64BD537 |
PackageArch | aarch64 |
PackageDescription | When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * 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 -- where pointers to malloc'd blocks are lost forever * Passing of uninitialised and/or unaddressable memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
PackageMaintainer | tv <tv> |
PackageName | valgrind |
PackageRelease | 1.mga9 |
PackageVersion | 3.20.0 |
SHA-1 | C1E49225ED222747AF16F362180FE43CC1F3D45A |
SHA-256 | 9E406DAB1D4D5470B312A91E1E123FA14450F8E0DEE230E8A320E4EE3CFF31C1 |