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

Doc: Fix typos

Browse Source 
Change-Id: I22b610a6dcab73867f915f877d7b7b844da5dc22
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>
This commit is contained in:
Leena Miettinen
2022-11-14 18:28:38 +01:00
parent 2d8dc4c779
commit be1aa6abed
21 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -62,7 +62,7 @@
breakpoint in the \uicontrol Breakpoints view.
At various times, attempts are made to implant pending breakpoints into
the debugged process. Succesfull implantation might create one or more
the debugged process. Successful implantation might create one or more
implanted breakpoints, each associated with an actual address in
the debugged breakpoint. The implantation might also move a breakpoint
marker in the editor from an empty line to the next line for which the
@@ -389,7 +389,7 @@
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
displaying a pointer to some private data structure, you see a list of
children, signals and slots.
children, signals, and slots.
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

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

@@ -169,7 +169,7 @@
The 32-bit CDB version can only debug 32-bit executables, whereas the 64-bit
version can debug both 64-bit and 32-bit executables. However, interrupting a
32-bit executable with a 64-bit debugger can result in a stacktrace of the
32-bit executable with a 64-bit debugger can result in a stack trace of the
WOW64 emulator 32-bit emulation layer being displayed.
\QC extends the command line debugger by loading the
@@ -187,7 +187,7 @@
It is highly recommended that you add the Symbol Server provided
by Microsoft to the symbol search path of the debugger. The
Symbol Server provides you with debugging informaton for the
Symbol Server provides you with debugging information for the
operating system libraries for debugging Windows applications.
For more information, see
\l{Setting CDB Paths on Windows}.

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

@@ -417,7 +417,7 @@
to manage the GDB process, see \l{Specifying GDB Settings} and
\l{Specifying Extended GDB Settings}.
For more informaton about connecting with \c {target extended-remote} mode
For more information about connecting with \c {target extended-remote} mode
in GDB, see \l{https://sourceware.org/gdb/onlinedocs/gdb/Connecting.html}
{Debugging with GDB: Connecting to a Remote Target}.