Lines Matching full:heap
479 In general, allocating large structures on the stack is a bad idea, because you can easily run out of stack space, especially on systems with limited memory or which expect to support large numbers of threads each with a small stack, and also because the error checking performed by Memcheck is more effective for heap\-allocated data than for stack\-allocated data\&. If you have to use this option, you may wish to consider rewriting your code to allocate on the heap rather than on the stack\&.
514 \fB\-\-max\-stackframe\fR, a requirement for a large stack is a sign of potential portability problems\&. You are best advised to place all large data in heap\-allocated memory\&.
765 \fIyes\fR, Memcheck keeps track of the origins of all uninitialised values\&. Then, when an uninitialised value error is reported, Memcheck will try to show the origin of the value\&. An origin can be one of the following four places: a heap block, a stack allocation, a client request, or miscellaneous other sources (eg, a call to
768 For uninitialised values originating from a heap block, Memcheck shows where the block was allocated\&. For uninitialised values originating from a stack allocation, Memcheck can tell you which function allocated the value, but no more than that \-\- typically it shows you the source location of the opening brace of the function\&. So you should carefully check that all of the function\*(Aqs local variables are initialised properly\&.
1160 \fB\-\-heap=<yes|no> [default: yes] \fR
1162 Specifies whether heap profiling should be done\&.
1165 \fB\-\-heap\-admin=<size> [default: 8] \fR
1167 If heap profiling is enabled, gives the number of administrative bytes per block to use\&. This should be an estimate of the average, since it may vary\&. For example, the allocator used by glibc on Linux requires somewhere between 4 to 15 bytes per block, depending on various factors\&. That allocator also requires admin space for freed blocks, but Massif cannot account for this\&.
1175 \fB\-\-pages\-as\-heap=<yes|no> [default: no] \fR
1187 Functions specified with this option will be treated as though they were a heap allocation function such as
1221 Any direct heap allocation (i\&.e\&. a call to
1231 call does not occur in an ignored function\&. This avoids the possibility of negative heap sizes if ignored blocks are shrunk with
1241 The significance threshold for heap allocations, as a percentage of total memory size\&. Allocation tree entries that account for less than this will be aggregated\&. Note that this should be specified in tandem with ms_print\*(Aqs option of the same name\&.
1251 The time unit used for the profiling\&. There are three possibilities: instructions executed (i), which is good for most cases; real (wallclock) time (ms, i\&.e\&. milliseconds), which is sometimes useful; and bytes allocated/deallocated on the heap and/or stack (B), which is useful for very short\-run programs, and for testing purposes, because it is the most reproducible across different machines\&.
1281 By default, Ptrcheck checks for overruns of stack, global and heap arrays\&. With
1282 \fI\-\-enable\-sg\-checks=no\fR, the stack and global array checks are omitted, and only heap checking is performed\&. This can be useful because the stack and global checks are quite expensive, so omitting them speeds Ptrcheck up a lot\&.
1289 Controls how Ptrcheck handles word\-sized, word\-aligned loads which partially overlap the end of heap blocks \-\- that is, some of the bytes in the word are validly addressable, but others are not\&. When
1292 (the default), loads from partially invalid addresses are treated the same as loads from completely invalid addresses: an illegal heap access error is issued\&.
