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

Doc: Describe "Force logging to console" Debugger option

Browse Source 
Task-number: QTCREATORBUG-25642
Change-Id: Iee1ad389294aadd372720bd3ddc8b4ebd07e7404
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2021-06-28 16:00:32 +02:00
parent ffd94f1138
commit 271ddaa510
2 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/qtcreator/images/qtcreator-debugger-general-options.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 19 KiB

After

Width:  |  Height:  |  Size: 21 KiB

8
doc/qtcreator/src/debugger/creator-only/creator-debugger-settings.qdocinc
View File

@@ -39,6 +39,14 @@
\l{Specifying Breakpoint Settings}{specify settings for breakpoints},
and map source paths to target paths.
You can view debug output in the \uicontrol {Debugger Log} view.
However, in some Linux distributions, such as Arch Linux, debug
output is sent to the system log. To override this behavior, select
the \uicontrol {Force logging to console} check box. This sets
\c QT_LOGGING_TO_CONSOLE=1 in the environment of the debugged
program, which effectively prevents storing debug output in
system logs.
\section2 Mapping Source Paths
To enable the debugger to step into the code and display the source code