Global error buffer race condition: SDL_GetError() thread-safety

SDL utilizes a global error-reporting mechanism where functions return a failure code, necessitating a call to SDL_GetError() to retrieve descriptive details. However, this global error buffer is not thread-safe.

In applications where multiple threads interact with SDL subsystems, an error generated in one thread can overwrite the message from another thread before the first thread can capture it. This creates a race condition where the string returned by SDL_GetError() may not correspond to the actual failure recently encountered by the calling context.

Is there a documented mechanism within SDL to provide thread-local error reporting? If not, what is the recommended pattern for safely capturing error strings across concurrent threads without data loss or overwriting?