Skip to content

Commit f1ab802

Browse files
committed
Fix typos
1 parent 23d09eb commit f1ab802

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

clang/docs/DebuggingCoroutines.rst

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -206,11 +206,11 @@ Tracking the exact suspension point
206206

207207
Among the compiler-generated members, the ``__coro_index`` is particularly
208208
important. This member identifies the suspension point at which the coroutine
209-
is currently suspended. However, it is non-trivial to map this number backto
209+
is currently suspended. However, it is non-trivial to map this number back to
210210
a source code location.
211211

212212
For GDB, the provided :ref:`gdb-script` already takes care of this and provides
213-
the exact line number of the suspension point as part of the couroutine handle's
213+
the exact line number of the suspension point as part of the coroutine handle's
214214
summary string. Unfortunately, LLDB's pretty-printer does not support this, yet.
215215
Furthermore, those labels are only emitted starting with clang 21.0.
216216

@@ -749,7 +749,7 @@ the suspension point.
749749
Line 45 of "llvm-example.cpp" starts at address 0x201b <_ZL9coro_taski.destroy+555> and ends at 0x2046 <_ZL9coro_taski.destroy+598>.
750750
Line 45 of "llvm-example.cpp" starts at address 0x253b <_ZL9coro_taski.cleanup+555> and ends at 0x2566 <_ZL9coro_taski.cleanup+598>.
751751

752-
LLDB does not support looking up labels, yet. That's also why LLDB's pretty-printer
752+
LLDB does not support looking up labels, yet. For this reason, LLDB's pretty-printer
753753
does not show the exact line number of the suspension point.
754754

755755

@@ -1014,13 +1014,11 @@ Note that this script requires LLDB 21.0 or newer.
10141014
GDB Debugger Script
10151015
-------------------
10161016

1017-
For GDB, the following script provides a couple of useful commands:
1018-
1019-
The following script provides
1017+
The following script provides:
10201018

10211019
* a pretty-printer for coroutine handles
10221020
* a frame filter to add coroutine frames to the built-in ``bt`` command
1023-
* the commands ``get_coro_frame`` and ``get_coro_promise`` to be used in
1021+
* the ``get_coro_frame`` and ``get_coro_promise`` functions to be used in
10241022
expressions, e.g. ``p get_coro_promise(fib.coro_hdl)->current_state``
10251023

10261024
It can be loaded into GDB using ``source gdb_coro_debugging.py``.

0 commit comments

Comments
 (0)