blob: eb3ea2992ac2510125352977a8f715b12547c1c9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
// Copyright (C) 2021 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
/*!
//! [settings valgrind]
\section1 Specifying Valgrind Settings
\QC integrates \l{Analyzing Code}{Valgrind code analysis tools} for
detecting memory leaks and profiling function execution. You can configure
the tools according to your needs.
You can specify Valgrind settings either globally for all projects or separately for each
project.
To specify Valgrind settings for the current project:
\list 1
\li In the \uicontrol {Valgrind Settings} section, select \uicontrol Custom.
\li Specify Valgrind settings for the project.
\image qtcreator-analyzer-settings.png "Valgrind Settings"
\li In \uicontrol {Valgrind executable}, specify the path to the
Valgrind executable.
\li In \uicontrol {Valgrind arguments}, specify additional arguments
for Valgrind.
\li In \uicontrol {Detect self-modifying code}, select whether to
detect self-modifying code and where to detect it: only on stack,
everywhere, or everywhere except in file-backend mappings.
\endlist
For more information about the CallGrind and MemCheck settings, see:
\list
\li \l{Selecting Profiling Options}
\li \l{Selecting Options for Memory Analysis}
\endlist
Click \uicontrol {Restore Global} to revert to the global settings.
To specify global Valgrind settings, select \uicontrol Edit >
\uicontrol Preferences > \uicontrol Analyzer.
//! [settings valgrind]
*/
|
