cudaGetErrorString 해석하기

A raw cudaError_t is just a number. To understand it, you translate it into plain English with cudaGetErrorString. 📖

cudaGetErrorString takes an error code and returns a human-readable C string describing exactly what went wrong.

Feed that string straight into printf so your logs say what happened instead of showing a cryptic integer.

One message you will meet often is out of memory, telling you a cudaMalloc asked for more than the device could give.

The string invalid configuration argument means your launch asked for too many threads or an illegal block or grid size.

An illegal address message points to an out-of-bounds access inside a kernel, often a missing bounds check on the index.

It shines inside your CUDA_CHECK macro: capture the code, then print its string so failures explain themselves at once.

There is also cudaGetErrorName, which returns the enum name like cudaErrorMemoryAllocation rather than the long description.

Use the name for compact logs and the description for clarity. Many teams print both to get the best of each.

Stuck on a fault? Paste the error string into a search engine. The wording is standard, so others have hit it before you.

Decoding turns a useless number into a clear clue. The right message often points you straight at the line you must repair.

Test your grasp of cudaGetErrorString.

cudaGetErrorString turns codes into readable messages, and cudaGetErrorName gives the enum name. Print them to debug with confidence. 🎉