From d46855ad5648202e21d8c09f42ae13d8c7d7fee2 Mon Sep 17 00:00:00 2001 From: youkaichao Date: Wed, 13 Aug 2025 11:33:06 +0800 Subject: [PATCH] typo fix Signed-off-by: youkaichao --- _posts/2025-08-11-cuda-debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2025-08-11-cuda-debugging.md b/_posts/2025-08-11-cuda-debugging.md index 6049886..68146a9 100644 --- a/_posts/2025-08-11-cuda-debugging.md +++ b/_posts/2025-08-11-cuda-debugging.md @@ -7,7 +7,7 @@ image: /assets/logos/vllm-logo-text-light.png # Introduction -Have you ever felt you are developing attention kernel and your tests oftens runs into illegal memory access (IMA for short) and you have no idea how to debug? We definitely felt this pain again and again while working on vLLM, a high-performance inference engine for LLM models. +Have you ever felt you are developing cuda kernels and your tests often run into illegal memory access (IMA for short) and you have no idea how to debug? We definitely felt this pain again and again while working on vLLM, a high-performance inference engine for LLM models. If you are one of the developers who have faced this issue, this blog is for you! We will uncover some of advanced debugging techniques we use that can help users debug complicated issues in vLLM, such as IMA.