Skip to content

Conversation

@kazutakahirata
Copy link
Contributor

No description provided.

@llvmbot llvmbot added clang Clang issues not falling into any other category coroutines C++20 coroutines labels Jul 5, 2025
@kazutakahirata kazutakahirata changed the title [lldb] Fix a typo in documentation [clang] Fix a typo in documentation Jul 5, 2025
@llvmbot
Copy link
Member

llvmbot commented Jul 5, 2025

@llvm/pr-subscribers-coroutines

@llvm/pr-subscribers-clang

Author: Kazu Hirata (kazutakahirata)

Changes

Full diff: https://github.com/llvm/llvm-project/pull/147128.diff

1 Files Affected:

  • (modified) clang/docs/DebuggingCoroutines.rst (+1-1)
diff --git a/clang/docs/DebuggingCoroutines.rst b/clang/docs/DebuggingCoroutines.rst
index 7ee4305c9c99a..8702152747c65 100644
--- a/clang/docs/DebuggingCoroutines.rst
+++ b/clang/docs/DebuggingCoroutines.rst
@@ -221,7 +221,7 @@ suspension point.
   Line 45 of "llvm-example.cpp" starts at address 0x201b <_ZL9coro_taski.destroy+555> and ends at 0x2046 <_ZL9coro_taski.destroy+598>.
   Line 45 of "llvm-example.cpp" starts at address 0x253b <_ZL9coro_taski.cleanup+555> and ends at 0x2566 <_ZL9coro_taski.cleanup+598>.
 
-LLDB does not support looking up labels. Furthmore, those labels are only emitted
+LLDB does not support looking up labels. Furthermore, those labels are only emitted
 starting with clang 21.0.
 
 For simple cases, you might still be able to guess the suspension point correctly.

Copy link
Member

@vogelsgesang vogelsgesang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kazutakahirata kazutakahirata merged commit 15f07db into llvm:main Jul 5, 2025
13 checks passed
@kazutakahirata kazutakahirata deleted the cleanup_20250704_doc_typo_lldb branch July 5, 2025 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clang Clang issues not falling into any other category coroutines C++20 coroutines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants