/****************************************************************************
**
** Copyright (C) 2019 The Qt Company Ltd.
** Contact: https://www.qt.io/licensing/
**
** This file is part of the Qt Creator documentation.
**
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and The Qt Company. For licensing terms
** and conditions see https://www.qt.io/terms-conditions. For further
** information use the contact form at https://www.qt.io/contact-us.
**
** GNU Free Documentation License Usage
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of
** this file. Please review the following information to ensure
** the GNU Free Documentation License version 1.3 requirements
** will be met: https://www.gnu.org/licenses/fdl-1.3.html.
**
****************************************************************************/

// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************

/*!
    \contentspage index.html
    \previouspage creator-troubleshooting-debugging.html
    \page creator-analyze-mode.html
    \nextpage creator-qml-performance-monitor.html

    \title Analyzing Code

    You can use the code analysis tools in the \uicontrol Debug mode. To
    switch to \uicontrol Debug mode, select \uicontrol Debug in the mode
    selector, or select the \uicontrol {Analyze} menu and then select a tool.
    When you are in the \uicontrol Debug mode, you can switch between tools by
    selecting them in the menu on the toolbar.

    You can drag and drop the views in the \uicontrol Debug mode to new
    positions on the screen. The size and position of views are saved for future
    sessions. Select \uicontrol {Window > Views > Reset to Default Layout} to
    reset the views to their original sizes and positions.

    You can use the following code analysis tools in the \uicontrol Debug
    mode:

    \list

        \li \l{Profiling QML Applications}{QML Profiler}

            You can inspect binding evaluations, signal handling, and
            painting operations when running QML code. This is useful for
            identifying potential bottlenecks, especially in the evaluation
            of bindings.

        \li \l{Using Valgrind Code Analysis Tools}{Valgrind Code Analysis Tools}

            You can detect problems in memory management by using the Memcheck
            tool and find cache misses in the code by using the Callgrind tool.

        \li \l{Using Clang Tools}{Clang Tools}

            You can detect problems in C, C++, and Objective-C programs by
            using Clang-Tidy and Clazy.

        \li \l{Detecting Memory Leaks with Heob}{Heob}

            You can use the Heob heap observer on Windows to detect buffer
            overruns and memory leaks.

        \li \l{Analyzing CPU Usage}{Performance Analyzer}

            You can analyze the CPU usage of embedded applications and Linux
            desktop applications with the Performance Analyzer that integrates
            the Linux Perf tool.

        \li \l{Analyzing Code with Cppcheck}{Cppcheck}

            You can use the experimental Cppcheck plugin to detect undefined
            behavior and dangerous coding constructs.

        \li \l{Visualizing Chrome Trace Events}{Chrome Trace Format Visualizer}

            You can use the Chrome Trace Format (CTF) Visualizer to view
            Chrome trace events. This is especially useful when viewing
            large trace files that are difficult to visualize using the
            built-in trace-viewer (\c{chrome://tracing}).
    \endlist

*/
