Proper handling of GetLastError (and others) in a multithreaded context

Question

Is it correct to assume that GetLastError (and variants) are per-thread or is it per-process? The problems if it is per-process are somewhat obvious in multithreaded apps because there is no way to guarentee that no other Win32 calls were made between your failed call and GetLastError. Sometimes the value of GetLastError is important.

For example, AcceptEx will return FALSE (failure) if you are using IO completion ports. WSAGetLastError (similar to GetLastError) will return ERROR_IO_PENDING to inform you that it is pended and the failure is not due to something else. The problem is that dozens of ofther calls can be in flight and overwrite this value.

Are these calls thread specific or process specific? If process specific then how do you handle this correctly?

Answer 1

the docs are absolutely unambiguous about this:

GetLastError Function

Retrieves the calling thread's last-error code value. The last-error code is maintained on a per-thread basis. Multiple threads do not overwrite each other's last-error code.

So they said it three times (in a single paragraph!): should be enough, as Lewis Carroll said;-). Thus there's no need to answer hypotheticals such as "but if it was per-process rather than per thread, then what about...?";-).

Answer 2

Both GetLastError and WSAGetLastError return per-thread error codes. Have a look at the MSDN entries:

• GetLastError: The return value is the calling thread's last-error code.
• WSAGetLastError: The WSAGetLastError function returns the last error that occurred for the calling thread.

Answer 3

You can read on MSDN (see http://msdn.microsoft.com/en-us/library/ms679360.aspx) clear answer on your question:

Retrieves the calling thread's last-error code value. The last-error code is maintained on a per-thread basis. Multiple threads do not overwrite each other's last-error code.