|
|
181.
|
|
|
<html><head/><body><p>When doing leak checking, determines how willing Memcheck is to consider different backtraces to be the same for the purposes of merging multiple leaks into a single leak report. When set to <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">low</span>, only the first two entries need match. When <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">med</span>, four entries have to match. When <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">high</span>, all entries need to match.</p><p>For hardcore leak debugging, you probably want to use <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">--leak-resolution=high</span> together with <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">--num-callers=40</span> or some such large number.</p><p>Note that the <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">--leak-resolution</span> setting does not affect Memcheck's ability to find leaks. It only changes how the results are presented.</p></body></html>
|
|
|
i18n: ectx: property (toolTip), widget (QComboBox, leakResolution)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:38
|
|
|
182.
|
|
|
Show leak kinds:
|
|
|
i18n: ectx: property (text), widget (QLabel, showLeakKindsLabel)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:60
|
|
|
183.
|
|
|
Specifies the leak kinds to show.
|
|
|
i18n: ectx: property (toolTip), widget (QPushButton, showLeakKinds)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:73
|
|
|
184.
|
|
|
Used heuristics:
|
|
|
i18n: ectx: property (text), widget (QLabel, leakCheckHeuristicsLabel)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:86
|
|
|
185.
|
|
|
<html><head/><body><p>Specifies the set of leak check heuristics to be used during leak searches. The heuristics control which interior pointers to a block cause it to be considered as reachable.</p></body></html>
|
|
|
i18n: ectx: property (toolTip), widget (QPushButton, leakCheckHeuristics)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:99
|
|
|
186.
|
|
|
Stacktraces keeping:
|
|
|
i18n: ectx: property (text), widget (QLabel, keepStacktracesLabel)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:109
|
|
|
187.
|
|
|
<html><head/><body><p>Controls which stack trace(s) to keep for malloc'd and/or free'd blocks. </p><p>With <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">alloc-then-free</span>, a stack trace is recorded at allocation time, and is associated with the block. When the block is freed, a second stack trace is recorded, and this replaces the allocation stack trace. As a result, any "use after free" errors relating to this block can only show a stack trace for where the block was freed. </p><p>With <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">alloc-and-free</span>, both allocation and the deallocation stack traces for the block are stored. Hence a "use after free" error will show both, which may make the error easier to diagnose. Compared to <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">alloc-then-free</span>, this setting slightly increases Valgrind's memory use as the block contains two references instead of one. </p><p>With <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">alloc</span>, only the allocation stack trace is recorded (and reported). With <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">free</span>, only the deallocation stack trace is recorded (and reported). These values somewhat decrease Valgrind's memory and cpu usage. They can be useful depending on the error types you are searching for and the level of detail you need to analyse them. For example, if you are only interested in memory leak errors, it is sufficient to record the allocation stack traces. </p><p>With <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">none</span>, no stack traces are recorded for malloc and free operations. If your program allocates a lot of blocks and/or allocates/frees from many different stack traces, this can significantly decrease cpu and/or memory required. Of course, few details will be reported for errors related to heap blocks. </p><p>Note that once a stack trace is recorded, Valgrind keeps the stack trace in memory even if it is not referenced by any block. Some programs (for example, recursive algorithms) can generate a huge number of stack traces. If Valgrind uses too much memory in such circumstances, you can reduce the memory required with the options <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">--keep-stacktraces</span> and/or by using a smaller value for the option <span style=" font-family:'Monospace'; font-weight:600; font-style:italic;">--num-callers</span>. </p></body></html>
|
|
|
i18n: ectx: property (toolTip), widget (QComboBox, keepStacktraces)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:122
|
|
|
188.
|
|
|
alloc
|
|
|
i18n: ectx: property (text), item, widget (QComboBox, keepStacktraces)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:126
|
|
|
189.
|
|
|
free
|
|
|
i18n: ectx: property (text), item, widget (QComboBox, keepStacktraces)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:131
|
|
|
190.
|
|
|
alloc-and-free
|
|
|
i18n: ectx: property (text), item, widget (QComboBox, keepStacktraces)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
tools/memcheck/configpage.ui:136
|
