Doc: Separate C++ and QML info about evaluating expressions

Also move info about inspecting basic Qt objects to a separate
session.

Change-Id: I60b0da446ad23cb76549d9ccf56bd9313c9a7127
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2019-07-23 11:52:42 +02:00
parent 9b1edfb371
commit 93c403e444
2 changed files with 20 additions and 6 deletions

View File

@@ -282,7 +282,14 @@
Note that functions used in the expressions are called each time, even if Note that functions used in the expressions are called each time, even if
they have side-effects. they have side-effects.
All backends support simple C and C++ expressions. Functions can be called The QML debugger can evaluate JavaScript expressions.
//! [debugger-expressions]
//! [debugger-expressions-cpp]
GDB, LLDB and CDB support the evaluation of simple C and C++ expressions.
Functions can be called
only if they are actually compiled into the debugged executable or a library only if they are actually compiled into the debugged executable or a library
used by the executable. Most notably, inlined functions such as most used by the executable. Most notably, inlined functions such as most
\c{operator[]} implementations of standard containers are typically \e{not} \c{operator[]} implementations of standard containers are typically \e{not}
@@ -318,6 +325,14 @@
however, can be recognized as such. however, can be recognized as such.
\endtable \endtable
\note The set of evaluated expressions is saved in your session.
//! [debugger-expressions-cpp]
//! [debugger-qt-basic-objects]
\section1 Inspecting Basic Qt Objects
The \uicontrol {Locals} and \uicontrol {Expressions} views also provide access The \uicontrol {Locals} and \uicontrol {Expressions} views also provide access
to the most powerful feature of the debugger: comprehensive display of data to the most powerful feature of the debugger: comprehensive display of data
belonging to Qt's basic objects. For example, in case of QObject, instead of belonging to Qt's basic objects. For example, in case of QObject, instead of
@@ -327,7 +342,7 @@
Similarly, instead of displaying many pointers and integers, \QC's debugger Similarly, instead of displaying many pointers and integers, \QC's debugger
displays the contents of a QHash or QMap in an orderly manner. Also, the displays the contents of a QHash or QMap in an orderly manner. Also, the
debugger displays access data for QFileInfo and provides access to the debugger displays access data for QFileInfo and provides access to the
"real" contents of QVariant. \e real contents of QVariant.
Right-click in the \uicontrol {Locals} or the \uicontrol {Expressions} view Right-click in the \uicontrol {Locals} or the \uicontrol {Expressions} view
to open a context menu that provides additional options for viewing data. The to open a context menu that provides additional options for viewing data. The
@@ -354,8 +369,5 @@
You can enable tooltips in the main editor displaying this information. You can enable tooltips in the main editor displaying this information.
For more information, see \l{Showing Tooltips in Debug Mode}. For more information, see \l{Showing Tooltips in Debug Mode}.
\note The set of evaluated expressions is saved in your session. //! [debugger-qt-basic-objects]
//! [debugger-expressions]
*/ */

View File

@@ -588,6 +588,8 @@
\include creator-debugger-common.qdocinc debugger-call-stack-trace \include creator-debugger-common.qdocinc debugger-call-stack-trace
\include creator-debugger-common.qdocinc debugger-locals \include creator-debugger-common.qdocinc debugger-locals
\include creator-debugger-common.qdocinc debugger-expressions \include creator-debugger-common.qdocinc debugger-expressions
\include creator-debugger-common.qdocinc debugger-expressions-cpp
\include creator-debugger-common.qdocinc debugger-qt-basic-objects
\section1 Directly Interacting with Native Debuggers \section1 Directly Interacting with Native Debuggers