luislavena/fenix — Issue #3: Make GetFullPathNameW multi-thread safe
Author: luislavena
Created: 2012-03-02 15:12:36+00:00
State: open

http://msdn.microsoft.com/en-us/library/windows/desktop/aa364963(v=vs.85).aspx

>Multithreaded applications and shared library code should not use the GetFullPathName function and should avoid using
>relative path names. The current directory state written by the SetCurrentDirectory function is stored as a global variable in
>each process, therefore multithreaded applications cannot reliably use this value without possible data corruption from other >threads that may also be reading or setting this value. This limitation also applies to the SetCurrentDirectory and >GetCurrentDirectory functions.

We need to do the same for `GetCurrentDirectoryW` too.