feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: Describe "Use target extended-remote to connect" option

Browse Source 
Task-number: QTCREATORBUG-25642
Change-Id: I6b40f0f900db5eb8a80ed21710a7ce57df2a9eda
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2021-07-01 09:12:13 +02:00
parent 7c0652b7ac
commit 32f67f6c83
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/qtcreator/images/qtcreator-debugger-start-external.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 13 KiB

9
doc/qtcreator/src/debugger/creator-only/creator-debugger.qdoc
View File

@@ -220,6 +220,15 @@
applications.
\li Select the \uicontrol {Break at "main"} check box to stop the
debugger at the main function.
\li Select the \uicontrol {Use target extended-remote to connect}
check box to create the connection in the
\c {target extended-remote mode}. In this mode, when the debugged
application exits or you detach from it, the debugger remains
connected to the target. You can rerun the application, attach
to a running application, or use monitor commands specific to the
target. For example, GDB does not exit unless it was invoked using
the \c {--once} option, but you can make it exit by using the
\c {monitor exit} command.
\li In the \uicontrol {Override SysRoot} field, specify the path to
the \c sysroot to use instead of the default \c sysroot.
\li In the \uicontrol {Debug information} field, specify the location