はてなブックマーク

To model concurrent activities. Assigning one thread to each activity can be a great simplification compared to multiplexing the states of multiple activities in a single thread. This is why most server software and embedded software is multithreaded. To use multiple CPU cores simultaneously for speeding up computations. This is why many High Performance Computing (HPC) applications are multithrea

To use this tool, specify --tool=cachegrind on the Valgrind command line. Cachegrind is a high-precision tracing profiler. It runs slowly, but collects precise and reproducible profiling data. It can merge and diff data from different runs. To expand on these characteristics: Precise. Cachegrind measures the exact number of instructions executed by your program, not an approximation. Furthermore,

To use this tool, you must specify --tool=callgrind on the Valgrind command line. Callgrind is a profiling tool that records the call history among functions in a program's run as a call-graph. By default, the collected data consists of the number of instructions executed, their relationship to source lines, the caller/callee relationship between functions, and the numbers of such calls. Optionall

Helgrind intercepts calls to many POSIX pthreads functions, and is therefore able to report on various common problems. Although these are unglamourous errors, their presence can lead to undefined program behaviour and hard-to-find bugs later on. The detected errors are: unlocking an invalid mutex unlocking a not-locked mutex unlocking a mutex held by a different thread destroying an invalid or a

Valgrind's Tool Suite The Valgrind distribution includes the following debugging and profiling tools: Memcheck Cachegrind Callgrind Massif Helgrind DRD DHAT Experimental Tools Other Tools Memcheck Memcheck detects memory-management problems, and is aimed primarily at C and C++ programs. When a program is run under Memcheck's supervision, all reads and writes of memory are checked, and calls to mal

Memcheck is a memory error detector. It can detect the following problems that are common in C and C++ programs. Accessing memory you shouldn't, e.g. overrunning and underrunning heap blocks, overrunning the top of the stack, and accessing memory after it has been freed. Using undefined values, i.e. values that have not been initialised, or that have been derived from other undefined values. Incor

Information About News Tool Suite Supported Platforms The Developers Source Code Current Releases Release Archive Variants / Patches Code Repository Valkyrie / GUIs Documentation Table of Contents Quick Start FAQ User Manual Download Manual Research Papers Books Contact Mailing Lists and IRC Bug Reports Feature Requests Contact Summary Commercial Support How to Help Contributing Project Suggestion