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

Doc: Describe new GDB options

Browse Source 
Task-number: QTCREATORBUG-25642
Change-Id: I32b5d9bffd0eab2dbc1f6afd1f05be149fe1a10e
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2021-06-28 17:09:13 +02:00
parent eb70e20453
commit 93be13bfc1
4 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/qtcreator/images/qtcreator-gdb-options.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 7.6 KiB

After

Width:  |  Height:  |  Size: 7.6 KiB

4
doc/qtcreator/src/debugger/creator-debugger-common.qdocinc
View File

@@ -162,6 +162,10 @@
editor, select \uicontrol GDB > \uicontrol {Adjust breakpoint locations} editor, select \uicontrol GDB > \uicontrol {Adjust breakpoint locations}
or \uicontrol CDB > \uicontrol {Correct breakpoint location}. or \uicontrol CDB > \uicontrol {Correct breakpoint location}.
When using GDB as backend, you can extend the ordinary GDB
breakpoint class by using Python. Select \uicontrol GDB >
\uicontrol {Use pseudo message tracepoints}.
When using CDB as backend, you can specify that the debugger should break on When using CDB as backend, you can specify that the debugger should break on
specific events, such as C++ exceptions, thread creation or exit, loading or specific events, such as C++ exceptions, thread creation or exit, loading or
unloading \l{Viewing Modules}{application modules}, or particular output. unloading \l{Viewing Modules}{application modules}, or particular output.

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

@@ -112,6 +112,10 @@
By default, GDB shows AT&T style disassembly. To switch to the Intel style, By default, GDB shows AT&T style disassembly. To switch to the Intel style,
select the \uicontrol {Use Intel style disassembly} check box. select the \uicontrol {Use Intel style disassembly} check box.
To have GDB automatically save a copy of its symbol index in a cache
on disk and retrieve it from there when loading the same binary in the
future, select the \uicontrol {Use automatic symbol cache} check box.
To execute GDB commands after GDB has been started, but before the debugged To execute GDB commands after GDB has been started, but before the debugged
program is started or attached, and before the debugging helpers are program is started or attached, and before the debugging helpers are
initialized, enter them in the \uicontrol {Additional Startup Commands} initialized, enter them in the \uicontrol {Additional Startup Commands}

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

@@ -1540,8 +1540,16 @@
\section1 Built-in Debugger Is Slow During Startup and Runtime \section1 Built-in Debugger Is Slow During Startup and Runtime
The part of the slowness that is related to the loading of debug information Slowness that is related to the loading of debug information is hard to
is hard to avoid. Another part stems from maintaining breakpoints inside avoid.
When using GDB as backend, you can automatically save a copy of
its symbol index in a cache on disk and retrieve it from there
when loading the same binary in the future. Select \uicontrol Tools
> \uicontrol Options > \uicontrol Debugger > \uicontrol GDB >
\uicontrol {Use automatic symbol cache}.
Some slowness stems from maintaining breakpoints inside
the debugger (under some circumstances all breakpoints need to be inserted the debugger (under some circumstances all breakpoints need to be inserted
and removed again for each step) and the evaluation of expressions after and removed again for each step) and the evaluation of expressions after
each step. We recommend that you minimize the number of breakpoints and each step. We recommend that you minimize the number of breakpoints and